Skip to main content

Connect Cursor

Cursor supports remote MCP servers natively. The OAuth flow is identical to ChatGPT and Claude — you sign in to SharedMemory once and Cursor remembers the connection.

Steps​

  1. Open Cursor → Settings → Tools & Integrations
  2. Scroll to MCP Servers and click Add new MCP server
  3. Choose HTTP (remote)
  4. Set the URL to: 
    https://api.sharedmemory.ai/mcp
  5. Click Connect. Cursor opens your default browser to the SharedMemory consent screen.
  6. Sign in, pick a default project, and click Allow.

The browser will deep-link back into Cursor (cursor://...) once authorization completes. The connection now appears as active in your MCP server list.

Verify​

Open the Cursor command palette (Cmd+Shift+P) and run "List MCP tools". You should see SharedMemory's tools — remember, query, get_entity, and friends.

How to use it​

Cursor's AI panel (the right sidebar) will use SharedMemory automatically when relevant. You can also nudge it directly:

"Search SharedMemory for our deploy process and use it as context for this PR."

"Save to SharedMemory: this repo uses Tailwind v4."

"Get the full profile of project api."

Why this is better than the stdio MCP server​

The local stdio MCP server (the original way to connect Cursor) requires an API key in your mcp.json and works only on the machine where you set it up. The remote OAuth connector:

  • Works on every Cursor install signed into the same SharedMemory account — no per-machine setup
  • Doesn't put API keys in disk-readable config files
  • Can be revoked centrally from the SharedMemory dashboard
  • Carries identity (Cursor → SharedMemory) so the Activity feed correctly attributes memories

If you're already using the stdio server, you can run them in parallel — Cursor will dedupe identical tool names, but the remote one is what you should standardize on.

Revoking access​

Open SharedMemory Dashboard → Connectors → Connected apps and click Revoke next to Cursor.

Troubleshooting​

"Could not return to Cursor" — Cursor uses the cursor://anysphere.cursor-deeplink/mcp/auth/callback redirect URI. If your OS blocks custom URL schemes (some Linux setups do), you'll have to copy the code= value from the URL bar manually. Open an issue if this happens — we'll add a fallback page.

Cursor says "MCP server timed out" — the first call after a long idle period may take a few hundred ms while we warm caches. Cursor's default timeout is generous; if you see this repeatedly, file a bug with the SharedMemory request id from the response header.