Cursor's setup is one file and one sign-in, and nothing about the file is a secret worth protecting.

Connect it

Add this to ~/.cursor/mcp.json to make it available in every project, or to .cursor/mcp.json in one repository to share it with just that project:

{
  "mcpServers": {
    "develosaur": {
      "url": "https://mcp.develosaur.com/v1/user/mcp"
    }
  }
}

Open Cursor Settings, MCP, and enable develosaur. The first time an agent actually uses it, Cursor opens the sign-in in your browser. Then just ask it something: "Read my develosaur board digest and tell me what is next."

What belongs in the file, and what does not

The file holds only the address. Never paste a token into mcp.json; access tokens expire on their own, and Cursor refreshes them without you doing anything, the same OAuth-only model covered in why Develosaur has no API keys to paste.

If the server shows red

Toggling it off and back on in Settings, MCP retries the sign-in, which covers most cases. A sign-in page that loops back usually means the email link opened in a different browser than the one that started the request; finish it in the same one. A corporate proxy or VPN blocking the callback usually clears on a retry off the network.

Sharing a board with something other than Cursor

Cursor and Claude Code can point at the same board at the same time. Both connect, both claim different tasks, and both see each other's changes live, the coordination described in several agents, one plan. Nothing about which client is attached changes how that works.

Full setup, troubleshooting and FAQ live on the Cursor integration page; more of these are on the blog.