pinecone:mcp
Reference for the Pinecone MCP server tools. Documents all available tools - list-indexes, describe-index, describe-index-stats, create-index-for-model, upsert-records, search-records, cascading-search, and rerank-documents. Use when an agent needs to understand what Pinecone MCP tools are available, how to use them, or what parameters they accept.
- License 许可
- MIT
- 最近更新
- 2026-11-13
- Stars
- ★ 29
- Forks
- 156
01 前言 Front Matter
- name
- pinecone:mcp
- description
- Reference for the Pinecone MCP server tools. Documents all available tools - list-indexes, describe-index, describe-index-stats, create-index-for-model, upsert-records, search-records, cascading-search, and rerank-documents. Use when an agent needs to understand what Pinecone MCP tools are available, how to use them, or what parameters they accept.
- allowed-tools
- Read
03 SKILL.md 正文
Pinecone MCP Tools Reference
The Pinecone MCP server exposes the following tools to AI agents and IDEs. For setup and installation instructions, see the MCP server guide.
Key Limitation: The Pinecone MCP only supports integrated indexes — indexes created with a built-in Pinecone embedding model. It does not work with standard indexes using external embedding models. For those, use the Pinecone CLI.
list-indexes
List all indexes in the current Pinecone project.
describe-index
Get configuration details for a specific index — cloud, region, dimension, metric, embedding model, field map, and status.
Parameters:
name(required) — Index name
describe-index-stats
Get statistics for an index including total record count and per-namespace breakdown.
Parameters:
name(required) — Index name
create-index-for-model
Create a new serverless index with an integrated embedding model. Pinecone handles embedding automatically — no external model needed.
Parameters:
name(required) — Index namecloud(required) —aws,gcp, orazureregion(required) — Cloud region (e.g.us-east-1)embed.model(required) — Embedding model:llama-text-embed-v2,multilingual-e5-large, orpinecone-sparse-english-v0embed.fieldMap.text(required) — The record field that contains text to embed (e.g.chunk_text)
upsert-records
Insert or update records in an integrated index. Records are automatically embedded using the index's configured model.
Parameters:
name(required) — Index namenamespace(required) — Namespace to upsert intorecords(required) — Array of records. Each record must have anidor_idfield and contain the text field specified in the index'sfieldMap. Do not nest fields undermetadata— put them directly on the record.
Example record:
{ "_id": "rec1", "chunk_text": "The Eiffel Tower was built in 1889.", "category": "architecture" }
search-records
Semantic text search against an integrated index. Pass plain text — the MCP embeds the query automatically using the index's model.
Parameters:
name(required) — Index namenamespace(required) — Namespace to searchquery.inputs.text(required) — The text queryquery.topK(required) — Number of results to returnquery.filter(optional) — Metadata filter using MongoDB-style operators ($eq,$ne,$in,$gt,$gte,$lt,$lte)rerank.model(optional) — Reranking model:bge-reranker-v2-m3,cohere-rerank-3.5, orpinecone-rerank-v0rerank.rankFields(optional) — Fields to rerank on (e.g.["chunk_text"])rerank.topN(optional) — Number of results to return after reranking
cascading-search
Search across multiple indexes simultaneously, then deduplicate and rerank results into a single ranked list.
Parameters:
indexes(required) — Array of{ name, namespace }objects to search acrossquery.inputs.text(required) — The text queryquery.topK(required) — Number of results to retrieve per index before rerankingrerank.model(required) — Reranking model:bge-reranker-v2-m3,cohere-rerank-3.5, orpinecone-rerank-v0rerank.rankFields(required) — Fields to rerank onrerank.topN(optional) — Final number of results to return after reranking
rerank-documents
Rerank a set of documents or records against a query without performing a vector search first.
Parameters:
model(required) —bge-reranker-v2-m3,cohere-rerank-3.5, orpinecone-rerank-v0query(required) — The query to rerank againstdocuments(required) — Array of strings or records to rerankoptions.topN(required) — Number of results to returnoptions.rankFields(optional) — If documents are records, the field(s) to rerank on
04 同仓库更多 Skills
business-data
暂无简介
workflow
Creates durable, resumable workflows using Vercel's Workflow SDK. Use when building workflows that need to survive restarts, pause for external events, retry on failure, or coordinate multi-step operations over time. Triggers on mentions of "workflow", "durable functions", "resumable", "workflow sdk", "queue", "event", "push", "subscribe", or step-based orchestration.
workflow
Vercel Workflow SDK expert guidance. Use when building durable workflows, long-running tasks, API routes or agents that need pause/resume, retries, step-based execution, or crash-safe orchestration with Vercel Workflow.
verification
Full-story verification — infers what the user is building, then verifies the complete flow end-to-end: browser → API → data → response. Triggers on dev server start and 'why isn't this working' signals.
vercel-storage
Vercel storage expert guidance — Blob, Global Config (formerly Edge Config), and Marketplace storage (Neon Postgres, Upstash Redis). Use when choosing, configuring, or using data storage with Vercel applications.
vercel-services
Configure and troubleshoot Vercel Services for multiple frontends and backends in one project. Use when composing a polyglot or multi-service application on one Vercel deployment; defining the `services` key, service-targeted rewrites, or service bindings in `vercel.json`; or running all services with `vercel dev`.