Sign inSign up

hackerdogs/pinecone-mcp

By hackerdogs

•Updated 4 months ago

Pinecone MCP Server

Image
0

411

hackerdogs/pinecone-mcp repository overview

Hackerdogs
hackerdogs ⁠

⁠Pinecone MCP Server

MCP server wrapper for Pinecone⁠ — managed vector database for semantic search, RAG, and AI application development.

⁠What is Pinecone?

Pinecone is a fully managed vector database optimized for storing and querying high-dimensional embeddings at scale. This MCP server (the official @pinecone-database/mcp package) lets AI assistants create and manage indexes, upsert vectors with metadata, run similarity queries, and build Retrieval-Augmented Generation (RAG) pipelines without leaving the conversation. See pinecone-io/pinecone-mcp⁠ for full documentation.

API key required — find yours at app.pinecone.io⁠.

Summary. Pinecone MCP Server — Dockerized from upstream @pinecone-database/mcp package.

⁠Tools Reference

ToolDescription
search-docsSearch Docs

⁠Example Prompts

Here are example prompts you can use with Claude (or any MCP client) when this tool is connected:

  • "List all my Pinecone indexes and their dimensions and metric types."
  • "Create a new Pinecone index called 'docs' with 1536 dimensions and cosine metric."
  • "Upsert these 5 text embeddings into the 'knowledge-base' index with source metadata."
  • "Query the 'products' index for the 10 most similar vectors to this embedding and return their metadata."
  • "Delete all vectors with the tag 'draft' from the 'articles' Pinecone index."
  • "Describe the stats for my 'support-tickets' index — how many vectors are stored and what namespaces exist?"

⁠Deploy

docker-compose up -d
⁠Docker Run (stdio mode)
docker run -i --rm \
  -e PINECONE_API_KEY \
  hackerdogs/pinecone-mcp:latest
⁠Docker Run (HTTP streamable mode)
docker run -d -p 8657:8657 \
  -e MCP_TRANSPORT=streamable-http \
  -e MCP_PORT=8657 \
  -e PINECONE_API_KEY \
  hackerdogs/pinecone-mcp:latest

⁠MCP Client Configuration

⁠Stdio mode (default)

Add to your Claude Desktop or Cursor MCP config:

{
  "mcpServers": {
    "pinecone-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "PINECONE_API_KEY",
        "hackerdogs/pinecone-mcp:latest"
      ],
      "env": {
        "MCP_TRANSPORT": "stdio",
        "PINECONE_API_KEY": ""
      }
    }
  }
}
⁠HTTP mode (streamable-http)

First, start the server using Docker Compose or docker run with HTTP mode (see Deploy⁠ above), then point your MCP client at the running server:

{
  "mcpServers": {
    "pinecone-mcp": {
      "url": "http://localhost:8657/mcp"
    }
  }
}

When to use HTTP mode: HTTP mode is ideal for shared/remote deployments, multi-user setups, and Hackerdogs⁠ scheduled prompts. The server runs as a long-lived process and accepts connections from multiple MCP clients concurrently.

⁠Environment Variables

VariableDefaultDescription
MCP_TRANSPORTstdioTransport mode: stdio or streamable-http
MCP_PORT8657HTTP port (only used with streamable-http)
PINECONE_API_KEY—Pinecone API key — find at app.pinecone.io⁠

⁠Installing in Hackerdogs

The fastest way to get started is through Hackerdogs⁠:

  1. Log in to your Hackerdogs account.
  2. Go to the Tools Catalog.
  3. Search for the tool by name.
  4. Expand the tool card and click Install — you're ready to go.

Give it a couple of minutes to go live. Then start querying by asking Hackerdogs to use the tool explicitly. If you don't specify, Hackerdogs will automatically choose the best tool for the job.

  1. Vendor API key required? Add your key in the config environment variable field before clicking Install. Your key will be encrypted at rest.
  2. Enable / Disable the tool anytime from the Enabled Tools page.
  3. Need to update a key or parameter? Go to My Tools → toggle Show Decrypted Values → edit → Save.

Want to contribute or chat with the team? Join our Discord⁠.

⁠Build

docker build -t hackerdogs/pinecone-mcp:latest .

⁠Testing

⁠Automated tests
./test.sh
⁠Test directly with Docker

1. Start the server in HTTP mode:

docker run -d --rm --name pinecone-mcp-test -p 8657:8657 \
  -e MCP_TRANSPORT=streamable-http \
  -e PINECONE_API_KEY \
  hackerdogs/pinecone-mcp:latest

2. Initialize the MCP session:

SESSION_ID=$(curl -s -D - -X POST http://localhost:8657/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"test","version":"0.1"}}}' \
  2>&1 | grep -i mcp-session-id | awk '{print $2}' | tr -d '\r\n')

curl -s -X POST http://localhost:8657/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: $SESSION_ID" \
  -d '{"jsonrpc":"2.0","method":"notifications/initialized"}'

3. List available tools:

curl -s -X POST http://localhost:8657/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -H "mcp-session-id: $SESSION_ID" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

4. Clean up:

docker stop pinecone-mcp-test

Tag summary

Content type

Image

Digest

sha256:b09aacde3…

Size

97.2 MB

Last updated

4 months ago

docker pull hackerdogs/pinecone-mcp