Skip to main content
Cursor configures remote MCP servers through a JSON file.

​
Where the file lives

A tunnel URL is usually project-specific, so the project file is normally the right one.

​
Add the connector

Then, in .cursor/mcp.json:
Remote servers use url rather than command. That’s the whole difference from a local stdio server.

​
With a bearer token

If you shared with --bearer:
.cursor/mcp.json in a project root is a file people commit. Don’t put a real token in one that’s tracked — either add it to .gitignore, or reference an environment variable with ${env:HEYMCP_BEARER} instead of hard-coding it.

​
Check it connected

Cursor’s MCP settings list each configured server with its status and lets you toggle them on and off. Your HeyMCP inspector is the better check though — you should see INIT, NOTIF and LIST rows fingerprinted as Cursor.

​
It’s not showing up

JSON syntax error, or the file is in the wrong place. .cursor/mcp.json has a leading dot, and it goes in the project root, not in .vscode/.
Cursor never reached the edge. Check the URL and that heymcp share is still running.
Your headers block is missing or the token doesn’t match what you passed to --bearer.