Add an MCP server to Cursor

Cursor talks to an MCP server over a URL (remote) or a command that runs on your machine (local). PlugMCP listings point at the publisher's own install, not a proxy. You add that URL or command to Cursor. The agent then lists tools and calls them.

One-click from a listing

1. Open the server page in the directory.
2. Copy the server URL if you want it, then click Add to Cursor. Cursor opens and asks you to install.
3. Allow the server. Open the MCP panel (Cursor Settings → MCP) and confirm it is on.
4. In a chat, ask the agent to list tools. You should see this server by name.

The deeplink is cursor://anysphere.cursor-deeplink/mcp/install with a base64 config. It carries the publisher's URL, or the local command if the listing is stdio-only.

Paste mcp.json yourself

If the deeplink does not open, create or edit .cursor/mcp.json in the project, or the user-level MCP file in Cursor Settings. A remote server looks like this:

{
  "mcpServers": {
    "context7": {
      "url": "https://mcp.context7.com/mcp"
    }
  }
}

A local (stdio) server uses a command instead of a URL. npm packages usually run through npx. Python packages use uvx. Containers use docker run.

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path"]
    }
  }
}

If it does not connect

• Remote URL returns 401: the server wants a key. Add a headers.Authorization field. The listing page says so when the probe sees auth required.
• Local command not found: install Node, uv, or Docker, depending on the package type on the listing.
• Tools list is empty: reload MCP in Cursor Settings, then ask the agent again. Some servers only expose tools after you sign in.

Claude, VS Code, Windsurf, ChatGPT, and Codex each have their own add path on the same listing. For Claude, see the companion guide.