Lets developers search Pinecone documentation and manage Pinecone indexes and data from their AI assistant.
Setup
Choose your client, copy the config, then fill in any required environment variables.
claude mcp add pinecone-developer --env PINECONE_API_KEY='<PINECONE_API_KEY>' -- npx -y @pinecone-database/mcp~/.codex/config.toml
[mcp_servers.pinecone-developer]
command = "npx"
args = ["-y", "@pinecone-database/mcp"]
env = { PINECONE_API_KEY = "<PINECONE_API_KEY>" }
# codex mcp add pinecone-developer --env PINECONE_API_KEY='<PINECONE_API_KEY>' -- npx -y @pinecone-database/mcp~/.cursor/mcp.json
{
"mcpServers": {
"pinecone-developer": {
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "<PINECONE_API_KEY>"
}
}
}
}.vscode/mcp.json
{
"servers": {
"pinecone-developer": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "<PINECONE_API_KEY>"
}
}
}
}~/.gemini/settings.json
{
"mcpServers": {
"pinecone-developer": {
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "<PINECONE_API_KEY>"
}
}
}
}claude_desktop_config.json
{
"mcpServers": {
"pinecone-developer": {
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "<PINECONE_API_KEY>"
}
}
}
}.trae/mcp.json
{
"mcpServers": {
"pinecone-developer": {
"command": "npx",
"args": [
"-y",
"@pinecone-database/mcp"
],
"env": {
"PINECONE_API_KEY": "<PINECONE_API_KEY>"
}
}
}
}Environment variables
PINECONE_API_KEY
Replace the placeholders with your own credentials and keep them out of version control.