# How to integrate Pinecone MCP with Claude Code ```json { "title": "How to integrate Pinecone MCP with Claude Code", "toolkit": "Pinecone", "toolkit_slug": "pinecone", "framework": "Claude Code", "framework_slug": "claude-code", "url": "https://composio.dev/toolkits/pinecone/framework/claude-code", "markdown_url": "https://composio.dev/toolkits/pinecone/framework/claude-code.md", "updated_at": "2026-03-29T06:45:37.839Z" } ``` ## Introduction Manage your Pinecone directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: - Via [Composio Connect](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_connect&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code) - Direct and easiest approach - Via [Composio SDK](https://docs.composio.dev/docs?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=composio_sdk) - Programmatic approach with more control ## Also integrate Pinecone with - [ChatGPT](https://composio.dev/toolkits/pinecone/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/pinecone/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/pinecone/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/pinecone/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/pinecone/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/pinecone/framework/codex) - [Cursor](https://composio.dev/toolkits/pinecone/framework/cursor) - [VS Code](https://composio.dev/toolkits/pinecone/framework/vscode) - [OpenCode](https://composio.dev/toolkits/pinecone/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/pinecone/framework/openclaw) - [Hermes](https://composio.dev/toolkits/pinecone/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/pinecone/framework/cli) - [Google ADK](https://composio.dev/toolkits/pinecone/framework/google-adk) - [LangChain](https://composio.dev/toolkits/pinecone/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/pinecone/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/pinecone/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/pinecone/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/pinecone/framework/crew-ai) ## TL;DR - Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles. - Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling. - Handling Large tool responses out of LLM context to minimize context rot. - Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need. ## Connect Pinecone to Claude Code ### Connecting Pinecone to Claude Code using Composio 1. Add the Composio MCP to Claude ```bash claude mcp add --scope user --transport http composio https://connect.composio.dev/mcp ``` ## What is Claude Code? Claude Code is Anthropic's command line developer tool that lets you use Claude directly inside your terminal. Instead of switching between your editor, browser, and chat, you can stay in your project folder and ask Claude to help you build, debug, refactor, and understand code right where you're working. Key features include: - Terminal-Native Experience: Work with Claude directly in your command line without switching contexts - MCP Support: Built-in support for Model Context Protocol servers to extend Claude's capabilities - Project Context: Claude understands your project structure and can read, write, and modify files - Interactive Development: Ask questions, debug code, and get help in real-time while coding - Multi-Platform: Works on macOS, Linux, WSL, and Windows ## What is the Pinecone MCP server, and what's possible with it? The Pinecone MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Pinecone account. It provides structured and secure access so your agent can perform Pinecone operations on your behalf. ## Supported Tools | Tool slug | Name | Description | |---|---|---| | `PINECONE_CANCEL_BULK_IMPORT` | Cancel Bulk Import | Tool to cancel a bulk import operation in Pinecone. Use when you need to stop an ongoing import operation that is not yet finished. | | `PINECONE_CONFIGURE_INDEX` | Configure Index | Tool to configure an existing Pinecone index, including pod type, replicas, deletion protection, and tags. Use when you need to scale an index vertically or horizontally, enable/disable deletion protection, or update tags. The change is asynchronous; check index status for completion. | | `PINECONE_CREATE_BACKUP` | Create Backup | Tool to create a backup of a Pinecone index for disaster recovery and version control. Use when you need to preserve the current state of an index including vectors, metadata, and configuration. | | `PINECONE_CREATE_INDEX` | Create Index | Tool to create a Pinecone index with specified configuration. Use when you need to initialize a new vector database index for storing and querying embeddings. | | `PINECONE_CREATE_INDEX_WITH_EMBEDDING_MODEL` | Create Index with Embedding Model | Tool to create a Pinecone index with integrated embedding model for automatic vectorization. Use when you need to set up a new index that automatically converts text to vectors using a pre-configured embedding model. | | `PINECONE_CREATE_INDEX_FROM_BACKUP` | Create Index from Backup | Tool to create an index from a backup. Use when you need to restore or duplicate index data from a previously saved backup. | | `PINECONE_CREATE_NAMESPACE` | Create Namespace | Tool to create a namespace within a serverless Pinecone index. Use when you need to organize vectors into isolated partitions. | | `PINECONE_DELETE_INDEX` | Delete Index | Tool to permanently delete a Pinecone index. Use when you need to remove an index from your project. Note: Deletion protection and pending collections can prevent deletion. | | `PINECONE_DELETE_NAMESPACE` | Delete Namespace | Tool to permanently delete a namespace from a serverless index. Use when you need to remove an entire namespace and all its data. This operation is irreversible and only supported on serverless indexes. | | `PINECONE_DESCRIBE_BACKUP` | Describe Backup | Tool to retrieve detailed information about a specific backup. Use when you need to check backup status, configuration, or metadata. | | `PINECONE_DESCRIBE_BULK_IMPORT` | Describe Bulk Import | Tool to describe a specific bulk import operation in Pinecone. Use when you need to retrieve detailed information about an import's status, progress, timing, and any errors. | | `PINECONE_DESCRIBE_INDEX_STATS` | Describe Index Stats | Tool to get index statistics including vector count per namespace, dimensions, and fullness. Use when you need to understand the contents and status of an index. | | `PINECONE_DESCRIBE_RESTORE_JOB` | Describe Restore Job | Tool to get detailed information about a specific restore job in Pinecone. Use when you need to check the status, progress, or metadata of a restore operation. | | `PINECONE_GENERATE_EMBEDDINGS` | Generate Embeddings | Tool to generate vector embeddings for input text using Pinecone's hosted embedding models. Use when you need to convert text into vector representations for semantic search or similarity matching. | | `PINECONE_GET_MODEL_INFORMATION` | Get Model Information | Tool to retrieve detailed information about a specific model hosted by Pinecone. Use when you need to understand model capabilities for embedding and reranking operations. | | `PINECONE_LIST_BULK_IMPORTS` | List Bulk Imports | Tool to list all recent and ongoing bulk import operations in Pinecone. Use when you need to monitor or track the status of data import jobs. Supports pagination with a default limit of 100 imports per page. | | `PINECONE_LIST_COLLECTIONS` | List Collections | Tool to list all collections in a Pinecone project (pod-based indexes only). Use when you need to view available collections. | | `PINECONE_LIST_INDEX_BACKUPS` | List Index Backups | Tool to list all backups for a specific Pinecone index. Use when you need to view available backups for an index. Supports pagination via limit and paginationToken parameters. | | `PINECONE_LIST_INDEXES` | List Indexes | Tool to list all indexes in a Pinecone project. Use when you need to retrieve all indexes with their configurations and status information. | | `PINECONE_LIST_AVAILABLE_MODELS` | List Available Models | Tool to list all available embedding and reranking models hosted by Pinecone. Use when you need to discover available models or filter by model type (embed/rerank) or vector type (dense/sparse). | | `PINECONE_LIST_NAMESPACES` | List Namespaces | Tool to list all namespaces in a serverless Pinecone index. Use when you need to discover available namespaces for data organization. Returns up to 100 namespaces by default with pagination support. | | `PINECONE_LIST_PROJECT_BACKUPS` | List Project Backups | Tool to list all backups for indexes in a Pinecone project. Use when you need to retrieve backup information across all project indexes. Supports pagination with limit and paginationToken parameters. | | `PINECONE_LIST_RESTORE_JOBS` | List Restore Jobs | Tool to list all restore jobs for a project with pagination support. Use when you need to view the status of restore operations or track restore progress. | | `PINECONE_LIST_VECTORS` | List Vectors | Tool to list vector IDs in a Pinecone serverless index. Use when you need to browse or retrieve vector identifiers from a namespace. Supports filtering by prefix and pagination for large result sets. | | `PINECONE_QUERY_VECTORS` | Query Vectors | Tool to perform semantic search within a Pinecone index using a query vector. Retrieves IDs and similarity scores of the most similar items, ordered from most to least similar. Either vector or id parameter must be provided. | | `PINECONE_RERANK_DOCUMENTS` | Rerank Documents | Tool to rerank documents by semantic relevance to a query. Use when you need to order retrieved documents by their semantic relevance to a user's search query using Pinecone's hosted reranking models. | | `PINECONE_SEARCH_RECORDS_IN_NAMESPACE` | Search Records in Namespace | Tool to search records within a Pinecone namespace using text, vector, or ID query. Use when you need to find similar records based on embeddings or record IDs. Results can optionally be reranked for relevance. | | `PINECONE_START_BULK_IMPORT` | Start Bulk Import | Tool to start an asynchronous bulk import of vectors from object storage (S3, GCS, or Azure Blob Storage) into a Pinecone index. Use when you need to import large volumes of vectors from external storage. Returns an import ID to track the operation status. | | `PINECONE_UPDATE_VECTOR` | Update Vector | Tool to update a vector in Pinecone by ID. Use to overwrite vector values and/or metadata. Supports bulk updates via metadata filters. | | `PINECONE_UPSERT_RECORDS_TO_NAMESPACE` | Upsert Records to Namespace | Tool to upsert text records into a Pinecone namespace. Use when you need to add or update records with automatic text-to-vector conversion. | ## Supported Triggers None listed. ## Creating MCP Server - Stand-alone vs Composio SDK The Pinecone MCP server is an implementation of the Model Context Protocol that connects Claude Code (and other AI assistants like Claude and Cursor) directly to your Pinecone account. It provides structured and secure access so Claude can perform Pinecone operations on your behalf. With Composio's managed implementation, you don't have to create your own developer app. For production, if you're building an end product, we recommend using your own credentials. The managed server helps you prototype fast and go from 0-1 faster. ## Step-by-step Guide ### 1. Prerequisites Before starting, make sure you have: - Claude Pro, Max, or API billing enabled Anthropic account - Composio API Key - A Pinecone account - Basic knowledge of Python or TypeScript ### 1. Install Claude Code To install Claude Code, use one of the following methods based on your operating system: ```bash # macOS, Linux, WSL curl -fsSL https://claude.ai/install.sh | bash # Windows PowerShell irm https://claude.ai/install.ps1 | iex # Windows CMD curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd ``` ### 2. Set up Claude Code Open a terminal, go to your project folder, and start Claude Code: - Claude Code will open in your terminal - Follow the prompts to sign in with your Anthropic account - Complete the authentication flow - Once authenticated, you can start using Claude Code ```bash cd your-project-folder claude ``` ### 3. Set up environment variables Create a .env file in your project root with the following variables: - COMPOSIO_API_KEY authenticates with Composio (get it from [Composio dashboard](https://dashboard.composio.dev/login?utm_source=toolkits&utm_medium=framework_template&utm_campaign=claude-code&utm_content=api_key&next=%2F~%2Forg%2Fconnect%2Fclients%2Fclaude-code)) - USER_ID identifies the user for session management (use any unique identifier) ```bash COMPOSIO_API_KEY=your_composio_api_key_here USER_ID=your_user_id_here ``` ### 4. Install Composio library No description provided. ```python pip install composio-core python-dotenv ``` ```typescript npm install @composio/core dotenv ``` ### 5. Generate Composio MCP URL No description provided. ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["pinecone"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http pinecone-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['pinecone'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http pinecone-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ### 6. Run the script and copy the MCP URL No description provided. ```python python generate_mcp_url.py ``` ```typescript node --loader ts-node/esm generate_mcp_url.ts # or if using tsx tsx generate_mcp_url.ts ``` ### 7. Add Pinecone MCP to Claude Code In your terminal, add the MCP server using the command from the previous step. The command format is: - claude mcp add registers a new MCP server with Claude Code - --transport http specifies that this is an HTTP-based MCP server - The server name (pinecone-composio) is how you'll reference it - The URL points to your Composio Tool Router session - --headers includes your Composio API key for authentication After running the command, close the current Claude Code session and start a new one for the changes to take effect. ```bash claude mcp add --transport http pinecone-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY" # Then restart Claude Code exit claude ``` ### 8. Verify the installation Check that your Pinecone MCP server is properly configured. - This command lists all MCP servers registered with Claude Code - You should see your pinecone-composio entry in the list - This confirms that Claude Code can now access Pinecone tools If everything is wired up, you should see your pinecone-composio entry listed: ```bash claude mcp list ``` ### 9. Authenticate Pinecone The first time you try to use Pinecone tools, you'll be prompted to authenticate. - Claude Code will detect that you need to authenticate with Pinecone - It will show you an authentication link - Open the link in your browser (or copy/paste it) - Complete the Pinecone authorization flow - Return to the terminal and start using Pinecone through Claude Code Once authenticated, you can ask Claude Code to perform Pinecone operations in natural language. For example: - "Query all vectors similar to user question" - "Upsert document embeddings into a namespace" - "Delete vectors from the archive index" ## Complete Code ```python import os from composio import Composio from dotenv import load_dotenv load_dotenv() COMPOSIO_API_KEY = os.getenv("COMPOSIO_API_KEY") USER_ID = os.getenv("USER_ID") composio_client = Composio(api_key=COMPOSIO_API_KEY) composio_session = composio_client.create( user_id=USER_ID, toolkits=["pinecone"], ) COMPOSIO_MCP_URL = composio_session.mcp.url print(f"MCP URL: {COMPOSIO_MCP_URL}") print(f"\nUse this command to add to Claude Code:") print(f'claude mcp add --transport http pinecone-composio "{COMPOSIO_MCP_URL}" --headers "X-API-Key:{COMPOSIO_API_KEY}"') ``` ```typescript import 'dotenv/config'; import { Composio } from '@composio/core'; const { COMPOSIO_API_KEY, USER_ID } = process.env; if (!COMPOSIO_API_KEY || !USER_ID) { throw new Error('COMPOSIO_API_KEY and USER_ID required in .env'); } const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY }); const composioSession = await composioClient.create(USER_ID, { toolkits: ['pinecone'], }); const composioMcpUrl = composioSession?.mcp.url; console.log(`MCP URL: ${composioMcpUrl}`); console.log(`\nUse this command to add to Claude Code:`); console.log(`claude mcp add --transport http pinecone-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`); ``` ## Conclusion You've successfully integrated Pinecone with Claude Code using Composio's MCP server. Now you can interact with Pinecone directly from your terminal using natural language commands. Key features of this setup: - Terminal-native experience without switching contexts - Natural language commands for Pinecone operations - Secure authentication through Composio's managed MCP - Tool Router for dynamic tool discovery and execution Next steps: - Try asking Claude Code to perform various Pinecone operations - Add more toolkits to your Tool Router session for multi-app workflows - Integrate this setup into your development workflow for increased productivity You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities. ## How to build Pinecone MCP Agent with another framework - [ChatGPT](https://composio.dev/toolkits/pinecone/framework/chatgpt) - [Antigravity](https://composio.dev/toolkits/pinecone/framework/antigravity) - [OpenAI Agents SDK](https://composio.dev/toolkits/pinecone/framework/open-ai-agents-sdk) - [Claude Agent SDK](https://composio.dev/toolkits/pinecone/framework/claude-agents-sdk) - [Claude Cowork](https://composio.dev/toolkits/pinecone/framework/claude-cowork) - [Codex](https://composio.dev/toolkits/pinecone/framework/codex) - [Cursor](https://composio.dev/toolkits/pinecone/framework/cursor) - [VS Code](https://composio.dev/toolkits/pinecone/framework/vscode) - [OpenCode](https://composio.dev/toolkits/pinecone/framework/opencode) - [OpenClaw](https://composio.dev/toolkits/pinecone/framework/openclaw) - [Hermes](https://composio.dev/toolkits/pinecone/framework/hermes-agent) - [CLI](https://composio.dev/toolkits/pinecone/framework/cli) - [Google ADK](https://composio.dev/toolkits/pinecone/framework/google-adk) - [LangChain](https://composio.dev/toolkits/pinecone/framework/langchain) - [Vercel AI SDK](https://composio.dev/toolkits/pinecone/framework/ai-sdk) - [Mastra AI](https://composio.dev/toolkits/pinecone/framework/mastra-ai) - [LlamaIndex](https://composio.dev/toolkits/pinecone/framework/llama-index) - [CrewAI](https://composio.dev/toolkits/pinecone/framework/crew-ai) ## Related Toolkits - [Supabase](https://composio.dev/toolkits/supabase) - Supabase is an open-source backend platform offering scalable Postgres databases, authentication, storage, and real-time APIs. It lets developers build modern apps without managing infrastructure. - [Composio](https://composio.dev/toolkits/composio) - Composio is an integration platform that connects AI agents with hundreds of business tools. It streamlines authentication and lets you trigger actions across services—no custom code needed. - [Codeinterpreter](https://composio.dev/toolkits/codeinterpreter) - Codeinterpreter is a Python-based coding environment with built-in data analysis and visualization. It lets you instantly run scripts, plot results, and prototype solutions inside supported platforms. - [GitHub](https://composio.dev/toolkits/github) - GitHub is a code hosting platform for version control and collaborative software development. It streamlines project management, code review, and team workflows in one place. - [Composio search](https://composio.dev/toolkits/composio_search) - Composio search is a unified web search toolkit spanning travel, e-commerce, news, financial markets, images, and more. It lets you and your apps tap into up-to-date web data from a single, easy-to-integrate service. - [Excel](https://composio.dev/toolkits/excel) - Microsoft Excel is a robust spreadsheet application for organizing, analyzing, and visualizing data. It's the go-to tool for calculations, reporting, and flexible data management. - [Perplexityai](https://composio.dev/toolkits/perplexityai) - Perplexityai delivers natural, conversational AI models for generating human-like text. Instantly get context-aware, high-quality responses for chat, search, or complex workflows. - [Browser tool](https://composio.dev/toolkits/browser_tool) - Browser tool is a virtual browser integration that lets AI agents interact with the web programmatically. It enables automated browsing, scraping, and action-taking from any AI workflow. - [21risk](https://composio.dev/toolkits/_21risk) - 21RISK is a web app built for easy checklist, audit, and compliance management. It streamlines risk processes so teams can focus on what matters. - [Ably](https://composio.dev/toolkits/ably) - Ably is a real-time messaging platform for live chat and data sync in modern apps. It offers global scale and rock-solid reliability for seamless, instant experiences. - [Abstract](https://composio.dev/toolkits/abstract) - Abstract provides a suite of APIs for automating data validation and enrichment tasks. It helps developers streamline workflows and ensure data quality with minimal effort. - [Abuselpdb](https://composio.dev/toolkits/abuselpdb) - Abuselpdb is a central database for reporting and checking IPs linked to malicious online activity. Use it to quickly identify and report suspicious or abusive IP addresses. - [Addressfinder](https://composio.dev/toolkits/addressfinder) - Addressfinder is a data quality platform for verifying addresses, emails, and phone numbers. It helps you ensure accurate customer and contact data every time. - [Agentql](https://composio.dev/toolkits/agentql) - Agentql is a toolkit that connects AI agents to the web using a specialized query language. It enables structured web interaction and data extraction for smarter automations. - [Agenty](https://composio.dev/toolkits/agenty) - Agenty is a web scraping and automation platform for extracting data and automating browser tasks—no coding needed. It streamlines data collection, monitoring, and repetitive online actions. - [Ai ml api](https://composio.dev/toolkits/ai_ml_api) - Ai ml api is a suite of AI/ML models for natural language and image tasks. It provides fast, scalable access to advanced AI capabilities for your apps and workflows. - [Aivoov](https://composio.dev/toolkits/aivoov) - Aivoov is an AI-powered text-to-speech platform offering 1,000+ voices in over 150 languages. Instantly turn written content into natural, human-like audio for any application. - [Alchemy](https://composio.dev/toolkits/alchemy) - Alchemy is a blockchain development platform offering APIs and tools for Ethereum apps. It simplifies building and scaling Web3 projects with robust infrastructure. - [Algolia](https://composio.dev/toolkits/algolia) - Algolia is a hosted search API that powers lightning-fast, relevant search experiences for web and mobile apps. It helps developers deliver instant, typo-tolerant, and scalable search without complex infrastructure. - [All images ai](https://composio.dev/toolkits/all_images_ai) - All-Images.ai is an AI-powered image generation and management platform. It helps you create, search, and organize images effortlessly with advanced AI capabilities. ## Frequently Asked Questions ### What are the differences in Tool Router MCP and Pinecone MCP? With a standalone Pinecone MCP server, the agents and LLMs can only access a fixed set of Pinecone tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Pinecone and many other apps based on the task at hand, all through a single MCP endpoint. ### Can I use Tool Router MCP with Claude Code? Yes, you can. Claude Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Pinecone tools. ### Can I manage the permissions and scopes for Pinecone while using Tool Router? Yes, absolutely. You can configure which Pinecone scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do. ### How safe is my data with Composio Tool Router? All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Pinecone data and credentials are handled as safely as possible. --- [See all toolkits](https://composio.dev/toolkits) · [Composio docs](https://docs.composio.dev/llms.txt)