Cline Setup

Add Memcone memory to Cline (VS Code extension) via the MCP settings panel.

Automatic setup (recommended)

Run this in your project directory:

bash
npx @memcone/cli link
npx @memcone/cli link

link detects Cline and writes the MCP config automatically. Reload VS Code and you're done.

You need a Memcone API key from dashboard → API keys. The CLI will prompt for it on first run and save it to ~/.memcone/credentials.

Manual config

  1. Open the Cline panel in VS Code
  2. Click the MCP Servers icon (plug icon in the top bar)
  3. Click Edit MCP Settings
  4. Add the Memcone entry:
json
{
  "mcpServers": {
    "memcone": {
      "type": "streamableHttp",
      "url": "https://memcone.com/api/mcp",
      "headers": {
        "Authorization": "Bearer mem_live_YOUR_KEY_HERE"
      }
    }
  }
}
{
  "mcpServers": {
    "memcone": {
      "type": "streamableHttp",
      "url": "https://memcone.com/api/mcp",
      "headers": {
        "Authorization": "Bearer mem_live_YOUR_KEY_HERE"
      }
    }
  }
}

Save and Cline will connect automatically — no restart needed.

Using it

Cline will call Memcone tools automatically when relevant:

  • memcone.context — injects your project identity, rules, and past session memory
  • memcone.remember — stores facts Cline learns about you
  • memcone.recall — searches past memory on demand

"Before you start, load my project memory."

"Remember that we use Vitest for all tests in this repo."

Troubleshooting

Memcone shows as disconnected → Make sure "type": "streamableHttp" is set. Cline v3+ requires this for remote HTTP servers.

401 Unauthorized → Verify your key at dashboard → API keys. It must start with mem_live_.

No memory returned → Nothing is stored yet. Ask Cline: "Remember that this project uses Next.js and Tailwind". Confirm at dashboard → Memory.