Skip to main content
Every Pinecone Assistant has a dedicated MCP server that gives AI agents direct access to context from the assistant’s uploaded files through the standardized Model Context Protocol (MCP). You can connect it to Claude Code, Claude Desktop, Cursor, or LangChain.
Pinecone also provides an MCP server for managing indexes, upserting data, and querying your Pinecone database directly from an AI agent. See Use the Pinecone MCP server.
There are two ways to connect to an assistant MCP server:
  • Remote MCP server - Use a dedicated MCP endpoint to connect directly to an assistant.
  • Local MCP server - Run a Docker container locally that connects to an assistant.
Both options support a context tool that allows agents to retrieve relevant context snippets from your assistant’s uploaded files. This is similar to the context API but fine-tuned for MCP clients. Additional capabilities, such as file access, will be added in future releases.

Remote MCP server

Every Pinecone Assistant has a dedicated MCP endpoint that you can connect directly to your AI applications. This option doesn’t require running any infrastructure and is managed by Pinecone. The MCP endpoint for an assistant is:
The previous SSE-based endpoint (with the /sse suffix) is no longer supported and returns HTTP 410. Use the streamable HTTP transport MCP endpoint, which implements the current MCP specification.

Prerequisites

Before you begin, make sure you have the following values:
  • <YOUR_PINECONE_API_KEY>: A Pinecone API key.
  • <YOUR_PINECONE_ASSISTANT_HOST>: In the Pinecone console, this is your assistant’s Host value.
  • <YOUR_ASSISTANT_NAME>: Your assistant’s name, as displayed in the Pinecone console. For example, example-assistant.

Use with Claude Code

You can use the Claude CLI to configure Claude Code to use your assistant’s remote MCP server. For more information, see Claude Code’s MCP documentation.
1

Add the MCP server using the Claude CLI

Replace <YOUR_PINECONE_API_KEY> with your Pinecone API key, <YOUR_PINECONE_ASSISTANT_HOST> with your Pinecone Assistant host, and <YOUR_ASSISTANT_NAME> with your assistant’s name.
2

Verify the server was added successfully

The MCP server tools are now available in Claude Code’s chat interface.

Use with Claude Desktop

You can configure Claude Desktop to use your assistant’s remote MCP server. However, at this early stage of remote MCP server adoption, the Claude Desktop application doesn’t support remote server URLs. The following example works around this with a local proxy server, supergateway, that forwards requests to the remote MCP server with your API key.
supergateway is an open-source third-party tool. Use at your own risk.
1

Open Claude Desktop settings

Open Claude Desktop and go to Settings.
2

Edit the config file

On the Developer tab, click Edit Config to open the configuration file.
3

Add the configuration

Replace <YOUR_PINECONE_API_KEY> with your Pinecone API key, <YOUR_PINECONE_ASSISTANT_HOST> with your Pinecone Assistant host, and <YOUR_ASSISTANT_NAME> with your assistant’s name.
4

Restart Claude Desktop

Save the configuration file and restart Claude Desktop.
From the new chat screen, a hammer (MCP) icon appears with the new MCP server available.

Use with Cursor

You can configure Cursor to use your assistant’s remote MCP server directly through the .cursor/mcp.json configuration file.
1

Create the .cursor directory

Open Cursor and create a .cursor directory in your project root if it doesn’t exist.
2

Open the config file

Open .cursor/mcp.json (create it if necessary). To learn more, refer to Cursor’s MCP documentation.
3

Add the configuration

Replace <YOUR_PINECONE_API_KEY> with your Pinecone API key, <YOUR_PINECONE_ASSISTANT_HOST> with your Pinecone Assistant host, and <YOUR_ASSISTANT_NAME> with your assistant’s name.Save the configuration file.
The MCP server tools are now available in Cursor’s chat interface.

Use with LangChain

You can use the LangChain MCP client to connect your assistants to a LangChain multi-agent workflow. For example, the following code integrates LangChain with two assistants, one called ai-news and the other called industry-reports:
Python

Local MCP server

Pinecone provides an open-source Pinecone Assistant MCP server that you can run locally with Docker. This option is useful for development, testing, or when you want to run the MCP server within your own infrastructure or expand the MCP server to include additional capabilities. For the most up-to-date information on the local MCP server, see the Pinecone Assistant MCP server repository.

Prerequisites

  • Docker is installed and running on your system.
  • A Pinecone API key. You can create a new key in the Pinecone console.
  • Your Pinecone Assistant host. To find it, go to your assistant in the Pinecone console. You’ll see the assistant Host in the sidebar.

Start the MCP server

1

Pull the Docker image

Download the assistant-mcp Docker image:
2

Start the server

Start the MCP server, providing your Pinecone API key and Pinecone Assistant host:

Use with Claude Desktop

1

Open Claude Desktop settings

Open Claude Desktop and go to Settings.
2

Edit the config file

On the Developer tab, click Edit Config to open the configuration file.
3

Add the configuration

Replace <YOUR_PINECONE_API_KEY> with your Pinecone API key and <YOUR_PINECONE_ASSISTANT_HOST> with your Pinecone Assistant host.
4

Restart Claude Desktop

Save the configuration file and restart Claude Desktop.
From the new chat screen, a hammer (MCP) icon appears with the new MCP server available.

Use with Cursor

1

Create the .cursor directory

Open Cursor and create a .cursor directory in your project root if it doesn’t exist.
2

Open the config file

Open .cursor/mcp.json (create it if necessary). To learn more, refer to Cursor’s MCP documentation.
3

Add the configuration

Replace <YOUR_PINECONE_API_KEY> with your Pinecone API key and <YOUR_PINECONE_ASSISTANT_HOST> with your Pinecone Assistant host.Save the configuration file.