Pinecone Assistant MCP Server

What is Pinecone Assistant MCP Server?

A lightweight MCP server that connects to Pinecone Assistant to fetch relevant information. It runs as a Docker container (or Rust binary) and supports returning multiple results based on a configurable limit.

How to use Pinecone Assistant MCP Server?

1. Docker build (optional)

   docker build -t pinecone/assistant-mcp .
   

2. Run the container

   docker run -i --rm \
     -e PINECONE_API_KEY=<YOUR_PINECONE_API_KEY> \
     -e PINECONE_ASSISTANT_HOST=<YOUR_PINECONE_ASSISTANT_HOST> \
     pinecone/assistant-mcp
   

   • PINECONE_API_KEY – required API key from Pinecone Console.
   • PINECONE_ASSISTANT_HOST – optional; defaults to https://prod-1-data.ke.pinecone.io.
   • LOG_LEVEL – optional logging level (default info).
3. Integration with Claude Desktop – add the server configuration to claude_desktop_config.json as shown in the README.
4. Run from source (requires Rust):

   cargo build --release
   ./target/release/assistant-mcp
   

5. Testing with the inspector (Node‑based tool):

   export PINECONE_API_KEY=...
   export PINECONE_ASSISTANT_HOST=...
   npx @modelcontextprotocol/inspector cargo run
   

Key Features

• Direct retrieval of information from Pinecone Assistant.
• Configurable number of results per query.
• Dockerized deployment for consistent runtime.
• Optional environment‑based logging control.
• Compatibility with Claude Desktop via MCP configuration.

Use Cases

• AI assistants that need up‑to‑date knowledge from Pinecone datasets.
• Enterprise search solutions leveraging Pinecone’s vector store.
• RAG (Retrieval‑Augmented Generation) pipelines where a fast, containerized retrieval service is required.
• Local development of AI agents that query Pinecone without exposing credentials.

FAQ

Q: Do I need a Pinecone account? A: Yes, you must have a Pinecone API key and an Assistant created in the Pinecone Console.

Q: Can I run the server without Docker? A: Absolutely. Clone the repo, install Rust, and use cargo build --release.

Q: How many results can I request? A: The server allows you to configure the limit; the default is defined in the source code (commonly 10).

Q: What logging levels are supported? A: error, warn, info (default), debug, and trace.

Q: Is there a way to test the server locally? A: Use the @modelcontextprotocol/inspector tool as demonstrated in the README.

Pinecone Assistant MCP Server

An MCP server implementation for retrieving information from Pinecone Assistant.

Features

• Retrieves information from Pinecone Assistant
• Supports multiple results retrieval with a configurable number of results

Prerequisites

• Docker installed on your system
• Pinecone API key - obtain from the Pinecone Console
• Pinecone Assistant API host - after creating an Assistant (e.g. in Pinecone Console), you can find the host in the Assistant details page

Building with Docker

To build the Docker image:

docker build -t pinecone/assistant-mcp .

Running with Docker

Run the server with your Pinecone API key:

docker run -i --rm \
  -e PINECONE_API_KEY=<YOUR_PINECONE_API_KEY_HERE> \
  -e PINECONE_ASSISTANT_HOST=<YOUR_PINECONE_ASSISTANT_HOST_HERE> \
  pinecone/assistant-mcp

Environment Variables

• PINECONE_API_KEY (required): Your Pinecone API key
• PINECONE_ASSISTANT_HOST (optional): Pinecone Assistant API host (default: https://prod-1-data.ke.pinecone.io)
• LOG_LEVEL (optional): Logging level (default: info)

Usage with Claude Desktop

Add this to your claude_desktop_config.json:

{
  "mcpServers": {
    "pinecone-assistant": {
      "command": "docker",
      "args": [
        "run", 
        "-i", 
        "--rm", 
        "-e", 
        "PINECONE_API_KEY", 
        "-e", 
        "PINECONE_ASSISTANT_HOST", 
        "pinecone/assistant-mcp"
      ],
      "env": {
        "PINECONE_API_KEY": "<YOUR_PINECONE_API_KEY_HERE>",
        "PINECONE_ASSISTANT_HOST": "<YOUR_PINECONE_ASSISTANT_HOST_HERE>"
      }
    }
  }
}

Building from Source

If you prefer to build from source without Docker:

1. Make sure you have Rust installed (https://rustup.rs/)
2. Clone this repository
3. Run cargo build --release
4. The binary will be available at target/release/assistant-mcp

Testing with the inspector

export PINECONE_API_KEY=<YOUR_PINECONE_API_KEY_HERE>
export PINECONE_ASSISTANT_HOST=<YOUR_PINECONE_ASSISTANT_HOST_HERE>
# Run the inspector alone
npx @modelcontextprotocol/inspector cargo run
# Or run with Docker directly through the inspector
npx @modelcontextprotocol/inspector -- docker run -i --rm -e PINECONE_API_KEY -e PINECONE_ASSISTANT_HOST pinecone/assistant-mcp

License

This project is licensed under the terms specified in the LICENSE file.