mcpField
P
Pinecone Assistant MCP Server

Pinecone Assistant MCP Server

Local
github.com/pinecone-ioAI & Agents46Updated 11w ago

About Pinecone Assistant MCP Server

Pinecone Assistant MCP Server is an MCP server for retrieving information from Pinecone Assistant. It is aimed at users who want MCP clients such as Claude to query a Pinecone Assistant, and it supports a configurable number of results.

Key features

  1. 01Retrieve information from Pinecone Assistant
  2. 02Configurable number of returned results
  3. 03Docker-based runtime
  4. 04Source build with Cargo

Use cases

  1. 01Querying Pinecone Assistant content from Claude Desktop
  2. 02Testing the server with MCP Inspector

MCP support

This is an MCP server that gives MCP clients the ability to retrieve information from Pinecone Assistant, and it can be added to claude_desktop_config.json.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"assistant": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"build"
]
}
}
}
Run commanddocker run -i --rm build

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
ocibuild

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.