Cursor MCP server: how to add and configure servers

Cursor reads MCP servers from mcp.json. It also runs two servers of its own: Origin MCP for repositories on Origin, and Cursor Cloud MCP for cloud-agent diagnostics.

Checked 3 October 2026 · from Cursor's MCP, Origin MCP and Cloud Agents documentation, and Cursor's 30 June 2026 changelog

One of 91 guides to monitoring and developer tools. Each covers what an AI coding agent can get out of the tool through MCP, the protocol that lets the agent query the tool directly.

How Cursor works with MCP

MCP connects an agent client to tools exposed by a server. In Cursor, you add the server for the system that holds the data, such as a database, issue tracker or monitoring product.

Cursor supports tools, prompts, resources, roots and elicitation. Roots tell a server which folders the client wants it to work in. They are a hint, not an access control. Elicitation lets a server ask the user a question mid-call.

Cursor also supports MCP Apps, a standard MCP extension that lets a tool return interactive UI. Hosts that cannot render that UI still get the normal tool response.

Origin MCP works in the opposite direction. Cursor is the server, and each tool acts as the authenticated caller, with the same permission checks as the Origin API.

Three surfaces with different setup and permissions

Every vendor here gets the same four checks: official, maintained, distributed and usable. Cursor passes 2 of them.

Most teams only need Cursor's client role: one server per system the agent should reach. Origin MCP and Cloud MCP matter when repositories live on Origin or agents run in Cursor's cloud.

What can an AI agent do with Cursor?

Do you need the MCP server at all?

Use a product's API or CLI when you need direct control over a supported operation. Use MCP when Cursor's agent should discover and invoke that product's tools.

In most clients each connected server's tool definitions take up context. Disable servers you are not using from Customize so their tools stay out of the session.

Cursor integration setup

Project servers go in .cursor/mcp.json and personal ones in ~/.cursor/mcp.json, both under the mcpServers key.

{"mcpServers":{"my-service":{
  "url":"https://api.example.com/mcp",
  "headers":{"Authorization":"Bearer ${env:MY_SERVICE_TOKEN}"}}}}

{"mcpServers":{"local-tools":{
  "type":"stdio",
  "command":"python",
  "args":["${workspaceFolder}/tools/mcp_server.py"],
  "env":{"API_KEY":"${env:API_KEY}"}}}}

Every other client

Each block below is the configuration for one client, with the file path and the key that client expects.

"auth":{
  "CLIENT_ID":"${env:MCP_CLIENT_ID}",
  "CLIENT_SECRET":"${env:MCP_CLIENT_SECRET}"}

${env:NAME}   ${userHome}   ${workspaceFolder}
${workspaceFolderBasename}   ${pathSeparator}  ${/}

command entries  ->  approve local stdio servers
URL entries      ->  approve remote HTTP/SSE servers
tool allowlists  ->  empty means every tool runs automatically

vscode.cursor.mcp.registerServer()

Read-only access, permissions and security

• For Origin investigation without writes, use the documented read-only route and retain repository permission boundaries.

• For external servers, review the endpoint's authentication and tools. Store credentials through ${env:NAME} interpolation or envFile rather than literal values.

• Cloud agents use MCP servers added through the MCP dropdown at cursor.com/agents, so a server in your local mcp.json may be missing there.

• An empty tool allowlist lets every tool from that server run automatically. Name tools explicitly to narrow it.

Troubleshooting

Connected, but no relevant tools appear

Check that you selected the correct surface and account. A transport handshake succeeds before any permission check on the requested data.

Origin does not work in another MCP client

Origin MCP currently supports Cursor and Grok Bot only. Other harnesses are listed as coming soon.

A server works in one project but not another

Check which file defines it. .cursor/mcp.json applies to its project, while ~/.cursor/mcp.json applies everywhere.

What the vendor documents

Cursor's MCP documentation states that "Allowlisting approves an MCP configuration. It does not distribute or install the server." Its Origin page says that tools "act as the authenticated caller".

Should you connect an agent to Cursor?

Yes. Add each data source's own server to Cursor, and use Origin MCP if your repositories are on Origin. Best for teams connecting a specific data source to a supported Cursor workflow.

Strongest fit

Yes. Add each data source's own server to Cursor, and use Origin MCP if your repositories are on Origin.

Main advantage

The editor can consume external tools while Origin provides a separate repository surface.

Main weakness

Origin is early beta with a restricted supported-client list.

Operational risk

Selecting the wrong surface or scope produces incomplete answers.

Frequently asked questions