Skip to content

MCP server

Pinecone MCP server

Pinecone's official developer MCP server lets AI search Pinecone docs, manage indexes, upsert records, search and rerank.

At a glance

Maintained by
Pinecone
Tools exposed
9 listed below
Reviewed
September 24, 2026

Why it matters

What it does and why it matters

Pinecone is a managed vector database used behind many AI search and knowledge features. Its developer MCP server helps developers build with it: search the Pinecone documentation, create and describe indexes, upsert records, search them and rerank results.

That shortens the path from idea to working retrieval, because a coding assistant can set up an index, load sample data and test searches in one conversation.

It can create indexes and upsert records, and we found no delete tools listed. Documentation search works without an API key, while index tools need one. Use a key for a development project while building, and keep production keys out of coding assistants.

Once the prototype works, we usually move loading and indexing into a proper pipeline, so the assistant searches but does not change production indexes.

Use cases

Best business use cases

Build retrieval faster

Set up an index and test searches while coding.

Docs answers

Answer Pinecone questions from its documentation.

Search testing

Try queries and reranking on sample data.

Index inspection

Check index settings and statistics.

RAG prototypes

Prototype a knowledge assistant quickly.

Tools

Available tools

Tool names as published by the maintainer at review time. Versions change, so check the repository for the current list.

Read and write: Read and write: can create indexes and upsert records; no delete tools listed.

  • search-docs

    Searches the official Pinecone documentation.

  • list-indexes

    Lists Pinecone indexes.

  • describe-index

    Describes an index's configuration.

  • describe-index-stats

    Shows statistics about data in an index.

  • create-index-for-model

    Creates an index with an integrated inference model.

  • upsert-records

    Inserts or updates records in an index.

  • search-records

    Searches records by text query.

  • cascading-search

    Searches across several indexes.

  • rerank-documents

    Reranks records or documents.

Workflows

Example workflows

Prototype a knowledge search

  1. 1

    Connect with a development API key.

  2. 2

    Ask the assistant to create an index with integrated embedding.

  3. 3

    Upsert a sample of documents.

  4. 4

    Run test searches and rerank results.

  5. 5

    Review quality before building the full pipeline.

Debug a search problem

  1. 1

    A user reports poor search results.

  2. 2

    Ask for the index statistics.

  3. 3

    Run the user query through search.

  4. 4

    Compare with cascading search and reranking.

  5. 5

    Adjust the setup based on the results.

Prompts

Example prompts

  • “Create an index for our help articles using integrated embedding.”

  • “Search the index for "how do I reset my password" and rerank the top ten.”

  • “How do namespaces work in Pinecone?”

Setup

Installation and configuration

Examples for Claude Desktop and Claude Code. Replace the placeholder values with your own keys, and store secrets outside version control.

Claude Desktop: claude_desktop_config.json

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

Claude Code: terminal

claude mcp add pinecone -e PINECONE_API_KEY="YOUR_API_KEY" -- npx -y @pinecone-database/mcp
  • Local server: stdio. npm: @pinecone-database/mcp.
  • Needs: PINECONE_API_KEY (needed for index tools; docs search works without it).

Security

Security considerations

  • Development keys

    Use keys for development projects in coding assistants.

  • Separate production

    Keep production indexes out of reach of experiments.

  • Data in indexes

    Avoid loading personal data into test indexes.

  • Review changes

    Check which indexes the assistant created.

Related servers

Servers that pair well with it

Qdrant

Qdrant's official MCP server gives AI a semantic memory: store information in a Qdrant collection and find it again by meaning.

Chroma

Chroma's official MCP server lets AI create collections, add, query, update and delete documents in a Chroma vector database, local or cloud.

Weaviate

An MCP server built into Weaviate that lets AI read collection settings, list tenants, run hybrid search and, when allowed, upsert objects.

Keep exploring

FAQ

Questions people ask us

Have a question that is not here? Ask us directly.

Start a project

Want this connected to your own systems? We build AI workflows with MCP.

Send a short brief. We reply with questions, a suggested plan and an estimate you can compare with other offers.

Your privacy choices

We use necessary storage to run this site. With your permission we also use Google Analytics to see which pages help people, and load maps from Google. You can change this at any time. Read the cookie policy.