Continue

Continue (continue.dev) speaks MCP over Streamable HTTP in Agent mode. Chat and Edit modes don’t reach MCP tools. Config is YAML, not JSON. 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 Continue-specific:

• An Engram API key. Generate one at app.engram.page/settings/api-keys. Continue doesn’t run an interactive OAuth flow for MCP servers, so the recipe below uses the Bearer-header path.

Endpoint

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

Setup

1. Add the YAML file. Create .continue/mcpServers/engram.yaml at your workspace root (project-scoped) or ~/.continue/mcpServers/engram.yaml (user global). Continue auto-loads any YAML file from those directories:

name: Engram
version: 0.0.1
schema: v1
mcpServers:
  - name: engram
    type: streamable-http
    url: https://mcp.engram.page/api/mcp
    requestOptions:
      headers:
        Authorization: Bearer ${{ secrets.ENGRAM_API_KEY }}

The ${{ secrets.X }} substitution pulls from Continue Hub secrets. For a plain-env-var path, write Bearer ${{ env.ENGRAM_API_KEY }} instead.

2. Reload if needed. Continue picks the file up automatically. If tools don’t appear, toggle the server off and on in the Continue panel’s MCP block, or reload your IDE window.

3. Switch to Agent mode. In the Continue panel, switch the mode dropdown to Agent. MCP tools are only available in Agent mode.

First-run auth

The Bearer header is sent on every request. There’s no interactive consent step. Test the connection by switching to Agent mode and asking Continue to call an Engram tool. If a result comes back, you’re authenticated.

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

Continue rules

Add a rules: block to your top-level config.yaml, or drop a markdown file under .continue/rules/. Continue feeds these into the system message. Use:

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 Agent mode, 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.

Continue 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

• Engram tools never appear in the picker. You’re in Chat or Edit mode. Switch the dropdown to Agent.
• YAML parse error on load. A standalone block file under mcpServers/ still needs the name, version, and schema fields at the top. The example above includes all three.
• 401 from Engram. The secret didn’t interpolate. Confirm the secret exists in Continue Hub (or that the env var is set), then reload your IDE window.

For cross-client failures, see Troubleshooting.

Revocation

To disconnect Continue from Engram:

1. In Continue, 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. Continue will need to re-authenticate to reconnect.

To drop it client-side, delete the YAML file and reload the IDE. To rotate the key, generate a new one in Engram settings and replace the secret value.

Next steps

MCP Protocol overview.

Scopes What the grant covers.

All integrations Pick a different client.