Pinecone, verified
MCP server by Pinecone · Verified
Search Pinecone docs and create, upsert into and query Pinecone indexes with integrated inference from your coding assistant.
Install Pinecone
Runs on your machine. Your client starts it with this command:
Needs Node.js on your computer. The setup steps below show where the command goes in each client.
PINECONE_API_KEYsecret optional Pinecone API key (index tools; docs search works without it).
Share this server
Opens this page, with the install command and setup steps.
mcp.tc/i/pineconeAbout
Connects an AI assistant to Pinecone projects and documentation. It can search the official Pinecone docs, list and describe indexes, create indexes that use an integrated embedding model, upsert records, and run text searches with metadata filtering and reranking.
Runs locally over stdio with npx and needs Node.js v20 or later. A Pinecone API key in PINECONE_API_KEY is needed to manage or query indexes; documentation search works without one. Only indexes with integrated inference are supported.
What you can do
- Search the official Pinecone documentation
- List and describe indexes and their statistics
- Create indexes backed by an integrated embedding model
- Upsert records into an index
- Search records with metadata filtering and reranking
- Search across multiple indexes with deduplication
- Rerank documents with a reranking model
Tools
Pinecone lists its tools only to clients with a key, so we can’t show them here.
Example prompts
Search the Pinecone docs for information about metadata filtering
List all my Pinecone indexes and describe their configurations
Create a new index called my-docs using the multilingual-e5-large model
What namespaces exist in my index, and how many records are in each?
Set up
Every client starts Pinecone on your machine with the same command. Pick yours; the page remembers your choice.
Claude Code
- Run this in a terminal, in your project folder:
claude mcp add --transport stdio pinecone --env "PINECONE_API_KEY=<YOUR_PINECONE_API_KEY>" -- npx -y @pinecone-database/mcp- Start Claude Code and type
/mcp. pinecone should show as connected.
Add --scope user to make it available in every project. Replace the placeholders with your own values.
Claude Desktop
- Open Settings → Developer → Edit Config. It opens
claude_desktop_config.json. Add:
{
"mcpServers": {
"pinecone": {
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "<YOUR_PINECONE_API_KEY>"
}
}
}
}- Save the file and restart Claude Desktop. Replace the placeholders with your own values.
Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.
Cursor
Add to Cursor (opens in a new tab)
Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):
{
"mcpServers": {
"pinecone": {
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "<YOUR_PINECONE_API_KEY>"
}
}
}
}Needs Node.js on your computer. Replace the placeholders with your own values.
VS Code
Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:
{
"servers": {
"pinecone": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "${input:pinecone-api-key}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "pinecone-api-key",
"description": "PINECONE_API_KEY",
"password": true
}
]
}Needs Node.js on your computer.
Devin Desktop
- Add it to
~/.config/devin/mcp_config.json(macOS and Linux) or%APPDATA%\devin\mcp_config.json(Windows):
{
"mcpServers": {
"pinecone": {
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "<YOUR_PINECONE_API_KEY>"
}
}
}
}- Refresh the MCP server list in Cascade. Replace the placeholders with your own values.
Devin Desktop is the new name for Windsurf.
Codex
codex mcp add pinecone --env "PINECONE_API_KEY=<YOUR_PINECONE_API_KEY>" -- npx -y @pinecone-database/mcpOr edit ~/.codex/config.toml directly:
[mcp_servers.pinecone]
command = "npx"
args = ["-y", "@pinecone-database/mcp"]
env = { PINECONE_API_KEY = "<YOUR_PINECONE_API_KEY>" }Needs Node.js on your computer. Replace the placeholders with your own values.
Gemini CLI
gemini mcp add -e "PINECONE_API_KEY=<YOUR_PINECONE_API_KEY>" pinecone npx -- -y @pinecone-database/mcpThis adds it to the current project. Add -s user to use it everywhere.
Any client
Most clients that start local servers accept this shape:
{
"mcpServers": {
"pinecone": {
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "<YOUR_PINECONE_API_KEY>"
}
}
}
}Zed puts servers under context_servers in its settings, with the same command, args and env fields.
Needs Node.js on your computer. Replace the placeholders with your own values.
FAQ
Can I paste mcp.tc/i/pinecone into my MCP client?
No. Pinecone runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y @pinecone-database/mcp.
Does Pinecone need an API key?
Yes. It reads PINECONE_API_KEY from its environment, and PINECONE_API_KEY is a secret. Put the value in your client’s config on your own machine, never in a shared file.
Is Pinecone a remote or a local server?
Local. Your client starts it as a process on your computer with npx -y @pinecone-database/mcp, which needs Node.js.
What can Pinecone do?
You can search the official Pinecone documentation, list and describe indexes and their statistics and create indexes backed by an integrated embedding model.
Which clients can use it?
Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.
Who wrote this page?
mcp.tc’s robot read Pinecone’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.
Embed
Show Pinecone in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work
README badge
[](https://mcp.tc/i/pinecone)<a href="https://mcp.tc/i/pinecone"><img src="https://mcp.tc/i/pinecone/badge.svg" alt="Pinecone on mcp.tc" height="20"></a>It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.
Website card
<script src="https://mcp.tc/w/pinecone.js" async></script>The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.
iframe
<iframe src="https://mcp.tc/embed/pinecone" title="Pinecone on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.
JSON
The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).
https://mcp.tc/i/pinecone.jsonmcp.tc isn’t affiliated with Pinecone. This page was built from Pinecone’s public metadata, last checked on 3 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.