← Back to directory
P

Pinecone MCP Server

Official
Connect your Pinecone projects to Cursor, Claude, and other AI assistants
GitHub source repository ↗
★ 71 Stars Category · Database Popular Source revision a15d4b9ebc2e
46FMRS · D
Reliability
5/20
Security and permissions
8/20
Maintenance
9/20
Documentation
12/20
Setup experience
12/20

This MCP server is designed for developers to integrate Pinecone with AI coding assistants. It offers a rich toolset covering documentation search, index management, data operations, and advanced search capabilities. Installation is straightforward, supporting Cursor, Claude Desktop, and Gemini CLI. However, it is limited to indexes with integrated inference; those needing other features should consider alternatives.

Read the FMRS scoring method →

The Pinecone Developer MCP Server enables AI assistants like Cursor, Claude Desktop, and Gemini CLI to interact with Pinecone projects and documentation. It supports searching documentation, managing indexes, performing data upserts and searches with integrated inference, and executing cross-index searches and reranking. The server is focused on improving the experience of developers working with Pinecone as part of their tech stack.

Tools

search-docs
Search the official Pinecone documentation.
list-indexes
Lists all Pinecone indexes.
describe-index
Describes the configuration of an index.
describe-index-stats
Provides statistics about the data in the index, including the number of records and available namespaces.
create-index-for-model
Creates a new index that uses an integrated inference model to embed text as vectors.
upsert-records
Inserts or updates records in an index with integrated inference.
search-records
Searches for records in an index based on a text query, using integrated inference for embedding. Has options for metadata filtering and reranking.
cascading-search
Searches for records across multiple indexes, deduplicating and reranking the results.
rerank-documents
Reranks a collection of records or text documents using a specialized reranking model.

Setup

Generate a Pinecone API key (from console). Ensure Node.js v18 or later is installed and that node and npx are in your PATH.

Configure Cursor: Create a .cursor/mcp.json file in the project root with the configuration (see install_config). Check status in Cursor Settings > MCP.

Configure Claude Desktop: Locate claude_desktop_config.json via Settings > Developer > Edit Config, add the configuration, then restart.

Use as a Gemini CLI extension: Run gemini extensions install https://github.com/pinecone-io/pinecone-mcp and set the PINECONE_API_KEY environment variable.

claude_desktop_config.json
{
  "mcpServers": {
    "pinecone": {
      "command": "npx",
      "args": [
        "-y",
        "@pinecone-database/mcp"
      ],
      "env": {
        "PINECONE_API_KEY": "<your pinecone api key>"
      }
    }
  }
}

Fit and risk

Best for

  • Developers who use Pinecone as part of their technology stack.
  • Users who want to manage Pinecone projects and indexes from within AI coding assistants.
  • Those needing to interact with Pinecone documentation or generate code based on configuration.

Not for

  • Users working with indexes without integrated inference, or requiring standalone embeddings, vector search, or assistant features.
  • Scenarios where you need to provide AI assistants with context from your knowledge base (use Pinecone's Assistant MCP for that).
  • Non-developer use cases or non-coding assistant environments.

Required permissions

  • Requires a PINECONE_API_KEY environment variable to access your Pinecone project.
  • Allows AI tools to create, list, describe, and delete indexes (actions depend on tool set).
  • Allows upserting and searching records, as well as cross-index search and reranking operations.
  • Allows searching official Pinecone documentation (no API key needed).

Risks and side effects

  • API key exposure: ensure the key is kept secure and not committed to version control.
  • Misoperations: AI assistants may accidentally create, modify, or delete indexes; authorize carefully.
  • Cost implications: index operations and data usage may incur charges; monitor usage.
  • Network dependency: requires access to api.pinecone.io; may fail behind firewalls.

Troubleshooting

  1. MCP server not appearing in your tool: check Node.js version, npx in PATH, config file location and JSON syntax, and restart the tool.
  2. Invalid API key or auth errors: verify key in console, check environment variable, ensure no extra spaces or quotes.
  3. Tools not working: confirm index has integrated inference; otherwise create a new one with an embedding model. Check MCP server logs.
  4. Connection issues: ensure firewall allows api.pinecone.io, or run the server manually for detailed errors.

Use cases

Search Pinecone documentation within coding assistants for accurate answers.
Configure indexes based on your application's needs and generate code informed by your index configuration and data.
Test queries by upserting and searching data in your dev environment, evaluating results.
List all your indexes, describe their configurations, and inspect data statistics and namespaces.
Search records using integrated inference, apply metadata filtering and reranking.

Supported clients

CursorFull support
Claude DesktopFull support
Gemini CLIFull support