Anysphere
Connect Cursor
Build with your pod's records, decisions and docs in context.
One-click install
RecommendedExpected to workchecked 1 Sept 2026The client supports what Synap needs; we have not run this path end to end recently.
- Click “Add to Cursor”.
- In Settings → MCP, click Connect next to synap and sign in.
- Ask: “list my Synap pods”. The first time, each pod returns a one-time approval link — open it and approve on your pod.
If something goes wrong
The connector is added but no pod data comes back.
Each pod must be approved once. Ask “list my Synap pods” — a pod that is not connected yet returns an approval link. Open it, approve on your pod, then ask again.
Tools appear but the agent never calls them.
Cursor uses MCP tools in Agent mode. Switch the chat to Agent.
Other ways to connect
With the Synap Cloud connectorExpected to workchecked 1 Sept 2026
- Add this to ~/.cursor/mcp.json:
{ "mcpServers": { "synap": { "url": "https://api.synap.live/mcp" } } } - In Settings → MCP, click Connect next to synap and sign in.
- Ask: “list my Synap pods”. The first time, each pod returns a one-time approval link — open it and approve on your pod.
If something goes wrong
The connector is added but no pod data comes back.
Each pod must be approved once. Ask “list my Synap pods” — a pod that is not connected yet returns an approval link. Open it, approve on your pod, then ask again.
Tools appear but the agent never calls them.
Cursor uses MCP tools in Agent mode. Switch the chat to Agent.
With the Synap CLIVerifiedchecked 24 Sept 2026
- Install the Synap CLI and sign in.
npm install -g @synap-core/cli && synap login - Write the client's MCP config and mint a dedicated agent key for your pod.
synap mcp connect cursor - Check the connection any time.
synap mcp verify
If something goes wrong
Tools appear but the agent never calls them.
Cursor uses MCP tools in Agent mode. Switch the chat to Agent.
Menus in other apps move; each way to connect shows the day its steps were last checked. Cursor documentation