Pinecone Assistant

Pinecone Assistant MCP server

rust

GitHub Stars

rust

Language

6 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

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

You have a Pinecone Assistant MCP Server that lets you retrieve information from Pinecone Assistant and return multiple results based on your configuration. This MCP server runs in a container and exposes a straightforward way to pass your Pinecone API credentials and the Assistant host so you can query Pinecone Assistant from your MCP client workflows.

How to use

Connect your MCP client to the Pinecone Assistant MCP Server to retrieve information from Pinecone Assistant. You’ll supply your Pinecone API key and the Pinecone Assistant host as environment variables when starting the server. You can configure the server to return multiple results, enabling richer responses from Pinecone Assistant.

How to install

Prerequisites you need before running the server are a Docker-capable environment, a Pinecone API key, and the Pinecone Assistant API host.

Step 1: Build the Docker image.

docker build -t pinecone/assistant-mcp .

Step 2: Run the server with your Pinecone credentials and target host.

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

Optional environment variable for logging detail levels is LOG_LEVEL. If you want more verbose output, set LOG_LEVEL to debug or info as needed.

Notes on credentials: replace the placeholder values with your actual Pinecone API key and the Assistant host you find in the Pinecone Console when viewing your Assistant details.

Additional notes and examples

If you are using Claude Desktop or other MCP clients, you can configure the MCP server entry to run inside Docker with the required environment variables. The server supports standard Docker-based invocation, so your MCP client will interact with it just like other remote MCP endpoints.

Testing and development can also be performed by using the inspector tool in conjunction with Docker to verify behavior before integrating into your client workflow.

Built by

VeilStrat

AI signals for GTM teams