Connecting Cursor
Configure Cursor's MCP support to consume the Subscriby server, by signing in or with a personal access token.
Requirements
- Cursor 0.46 or newer (MCP support GA).
- A Subscriby account. Cursor signs you in; a personal access token is only needed when you want a connection narrower than your own reach.
Config
Cursor's MCP configuration lives at ~/.cursor/mcp.json on macOS / Linux and %APPDATA%/Cursor/mcp.json on Windows.
Add the server
Open the config file and merge:
{
"mcpServers": {
"subscriby": {
"url": "https://mcp.subscriby.net"
}
}
}Restart Cursor.
Sign in
Open Settings → MCP. The subscriby entry shows Needs login; click it. Cursor opens Subscriby in your browser: sign in if you are not already, read the consent screen and press Authorize. Cursor picks up the connection and lists the tools.
Verify
Open Composer (or chat) and ask:
Using the subscriby server, list my projects.
Cursor shows the tool invocation in its sidebar. You can approve each call individually or toggle "auto-approve for session" on the subscriby namespace; tools that change or delete data are marked so Cursor asks first.
Using a personal access token instead
Mint a token in Settings → API Tokens with the abilities you want Cursor to exercise and send it as a header; Cursor then skips the sign-in:
{
"mcpServers": {
"subscriby": {
"url": "https://mcp.subscriby.net",
"headers": {
"Authorization": "Bearer sbt_live_YOUR_TOKEN"
}
}
}
}Project-scoped versus user-scoped
Cursor also supports per-workspace .cursor/mcp.json. If you want the subscriby integration only active inside a specific repo, put the config there instead of the global location. Useful when you have a repo-specific Subscriby automation you want the AI agent to help with.
Troubleshooting
- Stuck on "Needs login": the URL must be exactly
https://mcp.subscriby.net; finish the browser sign-in and return to Cursor, which retries on its own. - Tool list empty: check Cursor's "MCP" panel in the settings drawer for connection errors.
- 403 on a call with a personal access token: the token lacks that tool's ability. The response names it in
error.context.required_ability. - 404 on specific tools: the token's team or project scope does not include the entity you referenced — see the tools reference.
How is this guide?