MCP server Official

Cursor MCP

Connect Cursor to external tools and data via MCP servers configured in mcp.json or installed from the Cursor Marketplace.

Author
Cursor (Anysphere)
Works with
Cursor
Documented
Oct 2, 2026

What Cursor MCP is

Cursor connects to MCP servers over stdio, SSE or Streamable HTTP. Servers are installed from Customize or configured in mcp.json. Supported capabilities are tools, prompts, resources, roots, elicitation and MCP Apps.

What it does

How Cursor MCP plugs in: which agents run it and what it addsRUNS INYour agentCursorone host documentedMCP SERVER · OFFICIALCursor MCPConnect the agent to tools, data…4 install steps1 permission noteWHAT IT ADDSWhat it doesRuns local stdio servers and remo…Static OAuth client credentials i…Supports tools, prompts, resource…One-click install from the Cursor…agent → extension → new capability · from the official repository or docs
Where Cursor MCP runs and what it adds, from its documentation
  • Runs local stdio servers and remote SSE / Streamable HTTP servers
  • Static OAuth client credentials in mcp.json for providers without dynamic registration
  • Supports tools, prompts, resources, roots, elicitation and MCP Apps (interactive UI)
  • One-click install from the Cursor Marketplace; team marketplaces for admins

When to use it

Good fit

  • Give Cursor Agent access to GitHub, databases or internal APIs
  • Distribute approved MCP servers to a team

Not for

  • Anything needing no external data; MCP adds an auth and trust surface

How to install Cursor MCP

You need: Cursor

  1. Open Customize and browse the Cursor Marketplace, click Add to Cursor, authenticate with OAuth
  2. Or create mcp.json with an mcpServers entry
  3. For stdio use command/args/env; for remote use url/headers
  4. Restart or enable the server in Customize
Configuration example (from the official docs)
{
  "mcpServers": {
    "server-name": {
      "command": "npx",
      "args": ["-y", "mcp-server"],
      "env": { "API_KEY": "value" }
    }
  }
}

Permissions and security

What it can access

  • stdio servers run local commands; servers may receive API keys via env/headers

Security notes from the maintainers

  • Static OAuth CLIENT_SECRET can be placed in mcp.json; treat the file as sensitive

Review the source before granting an agent access to credentials or production systems. We document what the maintainers state; we do not audit code.

Tools it extends

Frequently asked questions

Which transports does Cursor MCP support?

stdio, SSE and Streamable HTTP. source

Where do I configure custom MCP servers in Cursor?

In mcp.json with an mcpServers object, or via the Customize page. source

Does Cursor support MCP Apps?

Yes; MCP tools can return interactive UI, with fallback to normal responses. source

Can I use OAuth with a fixed client ID in Cursor MCP?

Yes, add an auth object with CLIENT_ID, optional CLIENT_SECRET and scopes to a url-based entry. source

Related guides

Sources and gaps

Not stated by the maintainers: mcp.json file locations not extracted; repo_url is placeholder: Cursor is closed source; Public source repository (closed source or not verified).

More extensions to look at