Cursor

Cursor 0.45+ speaks Streamable HTTP MCP natively, so it connects directly to https://sync.buzz/mcp — no local bridge needed.

Prerequisites

• Cursor 0.45 or newer (HTTP MCP support).
• A personal access token (see Connect overview).

Configure

Cursor reads MCP servers from a per-workspace .cursor/mcp.json or the global ~/.cursor/mcp.json.

{
  "mcpServers": {
    "sync": {
      "type": "http",
      "url": "https://sync.buzz/mcp",
      "headers": {
        "Authorization": "Bearer sync_pat_YOUR_TOKEN_HERE"
      }
    }
  }
}

Replace sync_pat_YOUR_TOKEN_HERE with the token from Account → Tokens.

Reload Cursor. Open Settings → Features → MCP; sync should be listed with a green indicator.

Verify

In Cursor chat, ask:

What features are in this project?

Cursor's agent will call Sync's tools (sync_status, sync_search, sync_feature_load) and return real data.

Tips

• Commit .cursor/mcp.json without the token. Use an env var: change the header value to "Bearer ${SYNC_TOKEN}" and set SYNC_TOKEN per developer. Or keep the config in global ~/.cursor/mcp.json only and leave per-project config out of git.
• Narrow the token's scope in Account → Tokens to just the projects this repo touches — smaller blast radius if a config leaks.