- 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.
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: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.Add the MCP server using the Claude CLI
<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.Verify the server was added successfully
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.Open Claude Desktop settings
Edit the config file
Add the configuration
<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.Restart Claude Desktop
Use with Cursor
You can configure Cursor to use your assistant’s remote MCP server directly through the.cursor/mcp.json configuration file.
Create the .cursor directory
.cursor directory in your project root if it doesn’t exist.Open the config file
.cursor/mcp.json (create it if necessary). To learn more, refer to Cursor’s MCP documentation.Add the configuration
<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.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 calledai-news and the other called industry-reports:
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
Pull the Docker image
assistant-mcp Docker image:Start the server
Use with Claude Desktop
Open Claude Desktop settings
Edit the config file
Add the configuration
<YOUR_PINECONE_API_KEY> with your Pinecone API key and <YOUR_PINECONE_ASSISTANT_HOST> with your Pinecone Assistant host.Restart Claude Desktop
Use with Cursor
Create the .cursor directory
.cursor directory in your project root if it doesn’t exist.Open the config file
.cursor/mcp.json (create it if necessary). To learn more, refer to Cursor’s MCP documentation.Add the configuration
<YOUR_PINECONE_API_KEY> with your Pinecone API key and <YOUR_PINECONE_ASSISTANT_HOST> with your Pinecone Assistant host.Save the configuration file.