← Explore all mcp servers

RETRIEVAL AND GROUNDING / Pinecone

Pinecone Assistant MCP Server

Retrieves document snippets from a named Pinecone Assistant for an MCP client through one tool, run as a locally built Docker image or Rust binary.

“An MCP server implementation for retrieving information from Pinecone Assistant.”

01 / THE REASONING

Why this made the selection.

  • Published in Pinecone's own repository; the README at this commit documents a Claude Desktop block that runs the server in Docker with PINECONE_API_KEY and PINECONE_ASSISTANT_HOST passed through.
  • src/router.rs at the same commit registers a single tool, assistant_context, taking assistant_name, query and top_k (default 15); the LICENSE is MIT, Copyright (c) 2025 Pinecone.

02 / THE REVIEW RECORD

What we actually inspected.

Source review has boundaries.
A clear record is more useful than a “safe” badge.

Material inspected

  • README.md at 94eeaf4637cf927087aebbf1863550781c310ac5
  • LICENSE, Cargo.toml, src/main.rs and src/router.rs at the same commit

Our findings

  • src/main.rs serves MCP over a ByteTransport built on stdin and stdout and logs to stderr.
  • Cargo.toml names assistant-mcp 0.1.0, Rust edition 2024, using the mcp-server and mcp-spec 0.1 crates.

Not established by this review

  • docker build
  • cargo build
  • Any Pinecone Assistant call

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

Connect a server deliberately.

Upstream setup instructions ↗

DOCUMENTED COMMAND

docker build -t pinecone/assistant-mcp .

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

  1. Run the README command above in a clone of the repository to build the image. It was not run.
  2. Add the README's Claude Desktop block with PINECONE_API_KEY and the assistant host from the Pinecone console. Do not commit the key.

Before you start

  • Docker, or a Rust toolchain to build from source
  • A Pinecone API key and an existing Pinecone Assistant

Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

{
  "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>"
      }
    }
  }
}

04 / FOLLOW THE EVIDENCE

The source trail.

Our notes are separate from the original resource.
Check upstream before adopting a new version.

  1. https://github.com/pinecone-io/assistant-mcp/blob/94eeaf4637cf927087aebbf1863550781c310ac5/README.md

    Supports: Docker build and run, Claude Desktop configuration, Environment variables

  2. https://github.com/pinecone-io/assistant-mcp/blob/94eeaf4637cf927087aebbf1863550781c310ac5/src/router.rs

    Supports: assistant_context tool and parameters

  3. https://github.com/pinecone-io/assistant-mcp/blob/94eeaf4637cf927087aebbf1863550781c310ac5/src/main.rs

    Supports: stdin/stdout transport

  4. https://github.com/pinecone-io/assistant-mcp/blob/94eeaf4637cf927087aebbf1863550781c310ac5/Cargo.toml

    Supports: Crate assistant-mcp 0.1.0

  5. https://github.com/pinecone-io/assistant-mcp/blob/94eeaf4637cf927087aebbf1863550781c310ac5/LICENSE

    Supports: MIT License, Copyright (c) 2025 Pinecone

Evidence & Ask