Cline

Cline has a first-class MCP Servers panel in VS Code. It speaks Streamable HTTP natively, so Engram connects with a URL plus a Bearer header. Cline doesn’t run an interactive OAuth consent flow today; the recipe below uses an Engram API key. Protocol background lives at MCP.

Prerequisites

Before you start, confirm:

• You have an Engram account at app.engram.page.
• At least one vault is synced. Open the Obsidian plugin or the web app and confirm notes have synced within the last day.
• You can sign in via browser. The MCP auth flow opens a browser window.

Plus a Cline-specific:

• An Engram API key. Generate one at app.engram.page/settings/api-keys. Engram shows the full key once. Treat it like a password.

Endpoint

https://mcp.engram.page/api/mcp

Setup

1. Open the MCP Servers panel. In VS Code, open the Cline panel, click the MCP Servers icon (the stacked-server icon in the top toolbar), and switch to the Remote Servers tab. Or click Configure → Configure MCP Servers to edit the JSON directly.

2. Add the engram entry. Cline accepts the standard mcpServers wrapper; Streamable HTTP is inferred from the presence of url:

{
  "mcpServers": {
    "engram": {
      "url": "https://mcp.engram.page/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ENGRAM_API_KEY"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

3. Restart the server. Save. The server should turn green in the MCP Servers panel. If it doesn’t, click Restart on the server row, or run Developer: Reload Window from the command palette.

First-run auth

Cline sends the Bearer header on every request. There’s no interactive consent flow on first use. Test the connection by clicking the server’s tool list in the MCP Servers panel; if tools appear, you’re authenticated.

The grant is the full mcp scope. Granular per-action scopes are on the roadmap.

Cline rules

Add the snippet below to a .clinerules file at your workspace root (commit it to share with your team) or to Cline’s global settings in the panel.

Engram holds my personal notes. Treat it as your long-term memory of me. Search it when a question depends on context I might have shared before. Before saving or updating a note, ask first.

Try it

In a Cline task, ask:

• Search my vault for notes about the engineering interview process and summarize the top three.
• Find anything I wrote about embeddings in the last month.

Cline calls Engram’s search (or get_note, write_note, etc.) tool, pulls back results, and answers in-context. If the tool fires, you’re set.

Troubleshooting (Cline specific)

• Tools don’t appear after a config edit. The server didn’t restart. Click Restart on the server row in the MCP Servers panel, or run Developer: Reload Window.
• 401 from Engram. The API key is wrong, expired, or the header is malformed. Verify the value at app.engram.page/settings/api-keys.
• Timeouts on slow networks. Bump the request timeout in the MCP Servers panel settings; default is conservative.

For cross-client failures, see Troubleshooting.

Revocation

To disconnect Cline from Engram:

1. In Cline, find the connector or MCP server entry and remove it.
2. In Engram, open your account → API Keys & Sessions and revoke the matching session.
3. The OAuth token is invalidated server-side. Cline will need to re-authenticate to reconnect.

To drop it client-side, delete the engram entry from your Cline MCP config and reload the window. To rotate the key, generate a new one in Engram settings and replace the value.

Next steps

MCP Protocol overview.

Scopes What the grant covers.

All integrations Pick a different client.