Skip to content
Start free

Connect Cursor

Add FounderSync to Cursor with a url entry in mcp.json, then sign in and approve access in your browser.

On this page

Cursor connects to FounderSync as a remote MCP server. You add the URL to an mcp.json file, and Cursor handles sign-in with OAuth. Use https://mcp.foundersync.io/mcp for full access, or https://mcp.foundersync.io/mcp/readonly for an agent that can only read. See the overview for the difference.

Add the server#

Cursor reads MCP servers from one of two files:

  • .cursor/mcp.json in your project root, for a server that only that project uses.
  • ~/.cursor/mcp.json in your home directory, for a server available in every project.

Add a url entry under mcpServers:

json
{
  "mcpServers": {
    "foundersync": {
      "url": "https://mcp.foundersync.io/mcp"
    }
  }
}

If the file already has other servers, add FounderSync next to them inside the same mcpServers object. You can list both entries to have a read-only and a full-access server side by side.

You do not need an API key or a headers block. FounderSync does not accept static keys; it only accepts tokens issued through the sign-in flow below.

Sign in#

Cursor supports OAuth for servers that require it, using the authorization code flow with PKCE. Because FounderSync supports dynamic client registration, you do not need to register an app or paste a client ID. When Cursor asks you to sign in to the server, it sends you to FounderSync's consent screen at https://foundersync.io/oauth/consent:

  1. Sign in to FounderSync if you are not already.
  2. Check the agent name and what it can and cannot do.
  3. Click Allow access.

You return to Cursor, and the FounderSync tools become available to the agent. Cursor renews expired access tokens with a refresh token, and you may need to sign in again if a token cannot be renewed.

Manage and debug#

Open Customize in Cursor's sidebar to enable, disable or remove an MCP server. To see connection or sign-in errors, open the Output panel (Cmd+Shift+U on macOS), then choose MCP Logs.

Ask the agent to "call whoami in FounderSync" to confirm the connection. If you belong to more than one startup, tell it which one to work on.

Cursor's documentation does not describe the exact button you click to start sign-in for a server defined in mcp.json. If no prompt appears, check MCP Logs and make sure the server is enabled in Customize.

To stop Cursor's access later, see security and access.