Add the Pinecone MCP server to Cursor

Config last verified Jun 1, 2026

The exact config to run Pinecone in Cursor — paste it in, restart, and the tools load.

Prerequisites

Cursor installed.
PINECONE_API_KEY — Pinecone API key from the Pinecone console, used by the developer MCP server. Required.

Setup

1. Open `~/.cursor/mcp.json`

2. Add this configuration

Add to ~/.cursor/mcp.json

~/.cursor/mcp.json

json

{
  "mcpServers": {
    "pinecone": {
      "command": "npx",
      "args": [
        "-y",
        "@pinecone-database/mcp"
      ],
      "env": {
        "PINECONE_API_KEY": "<PINECONE_API_KEY>"
      }
    }
  }
}

3. Restart Cursor and confirm the Pinecone tools load.

Gotchas

Cursor keeps MCP servers under an "mcpServers" object in ~/.cursor/mcp.json for global use, and also reads a project-scoped .cursor/mcp.json so a repository can ship its own servers. Remote servers are configured with a bare "url" field and connect natively, with OAuth handled in-app when a server requires it.

← Back to the Pinecone MCP server