Pinecone Plugin for Claude Code
Official Pinecone plugin: an agent creates indexes, searches them, builds a RAG assistant and cites your files.
- 68 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent creates indexes, writes records and uploads files into the Pinecone account with your key.
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/pinecone-plugin-for-claude-codeDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent creates indexes, writes records and uploads files into the Pinecone account with your key.
This is third-party code. Review the repository files before installing.
What it does
The plugin adds the Pinecone vector database to Claude Code: an MCP server with seven tools and a set of skills. Through MCP the agent lists and describes indexes, searches records with filters and reranking, creates an index with integrated embeddings and upserts records. Skills run as commands like `/pinecone:query`, `/pinecone:quickstart` and `/pinecone:assistant`. The last one creates a Pinecone Assistant from a folder of documents, syncs files and answers with citations. `/pinecone:full-text-search` walks through the document schema, ingestion and BM25 queries with hybrid search. At session start a hook checks that `PINECONE_API_KEY` is set.
Who it is for. Developers of RAG and semantic search on Pinecone who want to run indexes and a document assistant from a Claude Code session.
Good fit when
- A new Pinecone project starts from zero: index, data load, first query.
- Product documentation must become an assistant that answers with citations.
- A folder of files was updated and the assistant needs a sync.
- Index search is built in natural language with reranking and filters.
- A team adopts BM25 full-text search alongside vector search.
Not a fit when
- A different vector database is used, such as Qdrant or Weaviate: the plugin only works with Pinecone.
- Indexes use embeddings from an outside provider: `/query` is built for Pinecone hosted models.
- `uv` is missing and cannot be installed, and assistant commands do not run without it.
Example request
Create a Pinecone Assistant from the `./docs` folder, upload the files and ask how authentication is configured in the project.Limitations
A Pinecone key in `PINECONE_API_KEY` and a Claude Code restart after install are required. Assistant commands need `uv` installed, and the MCP server starts through `npx`, so Node.js is required. `/pinecone:query` works only with integrated indexes on Pinecone hosted embedding models. The full-text search skill relies on the preview API `2026-01.alpha` and the `pinecone` Python SDK 9.0 or newer. The last repository commit dates from September 2026.
How to disable. Disable the plugin in `/plugin` and remove `PINECONE_API_KEY` from the environment. Indexes and assistants stay in the Pinecone account and are deleted there.
FAQ
How do I install the plugin?
Run `/plugin install pinecone` from the Claude Code plugin directory and restart. The fallback is `/plugin marketplace add pinecone-io/pinecone-claude-code-plugin`, then `/plugin install pinecone@pinecone-claude-code-plugin`.
Why do assistant commands fail?
Most likely `uv` is not installed. Install it, restart the terminal and verify with `uv --version`.
What if I get an "API Key not found" error?
Set `PINECONE_API_KEY` in the environment and restart Claude Code. You can check the value with `echo $PINECONE_API_KEY`.
Which tools does the MCP server give?
Seven: `list-indexes`, `describe-index`, `describe-index-stats`, `search-records`, `create-index-for-model`, `upsert-records` and `rerank-documents`.
How do `/pinecone:query` and `/pinecone:assistant` differ?
`/pinecone:query` searches Pinecone indexes, while `/pinecone:assistant` works with an assistant: it creates one, uploads files, syncs and answers with citations.
Discussion
No questions or reviews yet.
Related
PluginsNine Pinecone skills: the agent creates a vector index, loads data, searches it and builds an assistant for documents
Official Pinecone MCP server: documentation search, index creation, record upserts and search from your agent
Monte Carlo plugin for Claude Code and Cursor: table checks before queries, data incident triage and monitor creation.
A Claude Code plugin and MCP server: over 1000 scientific tools for biology, chemistry and medicine, data-check commands and routing skills
Semantica plugin: 17 skills and 3 agents for knowledge graphs, reasoning and data provenance in Claude Code, Cursor and Codex.
A local MCP server that turns a folder of documents into a knowledge base with hybrid search for Claude Code and Cursor
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Authentication | Repository stars | Main difference |
|---|---|---|---|---|
| Pinecone Plugin for Claude Code (this card) | yes | API key | 68 | |
| Pinecone Developer MCP Server | yes | key is optional | 72 | only the Pinecone MCP server; the plugin adds skills, an assistant and a key check to it |
| Pinecone Agent Skills | yes | 15 | a skill set without the plugin and MCP; here everything ships in one Claude Code install |
README in short
The README gives two install paths, lists the plugin skills and the seven MCP server tools, and ends with common errors: key, `uv`, integrated indexes.