How to integrate Pinecone MCP with Codex

GET STARTED FOR FREE
Framework Integration Gradient
Pinecone Logo
Codex Logo
divider

Introduction

Codex is one of the most popular coding harnesses out there. And MCP makes the experience even better. With Pinecone MCP integration, you can draft, triage, summarise emails, and much more, all without leaving the terminal or app, whichever you prefer.

Composio removes the Authentication handling completely from you. We handle the entire integration lifecycle, and all you need to do is just copy the URL below, authenticate inside Codex, and start using it.

Why use Composio?

Apart from a managed and hosted MCP server, you will get:

  • CodeAct: A dedicated workbench that allows GPT to write its code to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool responses: Handle them to minimise context rot.
  • Dynamic just-in-time access to 20,000 tools across 870+ other Apps for cross-app workflows. It loads the tools you need, so GPTs aren't overwhelmed by tools you don't need.

How to install Pinecone MCP in Codex

Codex CLI

Run the command in your terminal.

Terminal

This will auto-redirect you to the Rube authentication page.

Rube authentication redirect page

Once you're authenticated, you will be able to access the tools.

Verify the installation by running:

codex mcp list

If you otherwise prefer to use config.toml, add the following URL to it. You can get the bearer token from rube.app → Use Rube → MCP URL → Generate token

[projects."/home/user/composio"]
trust_level = "untrusted"

[mcp_servers.rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex in VS Code

If you have installed Codex in VS Code.

Then: ⚙️ → MCP Settings → + Add servers → Streamable HTTP:

Add the Rube MCP URL: https://rube.app/mcp and the bearer token.

VS Code MCP Settings

To verify, click on the Open config.toml

Open config toml in Codex

Make sure it's there:

[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"

Codex App

Codex App follows the same approach as VS Code.

  1. Click ⚙️ on the bottom left → MCP Servers → + Add servers → Streamable HTTP:
Codex App MCP Settings
  1. Restart and verify if it's there in .codex/config.toml
[mcp_servers.composio_rube]
bearer_token_env_var = "your bearer token"
enabled = true
url = "https://rube.app/mcp"
  1. Save, restart the extension, and start working.

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 & Triggers

Tools
Cancel Bulk ImportTool to cancel a bulk import operation in Pinecone.
Configure IndexTool to configure an existing Pinecone index, including pod type, replicas, deletion protection, and tags.
Create BackupTool to create a backup of a Pinecone index for disaster recovery and version control.
Create IndexTool to create a Pinecone index with specified configuration.
Create Index with Embedding ModelTool to create a Pinecone index with integrated embedding model for automatic vectorization.
Create Index from BackupTool to create an index from a backup.
Create NamespaceTool to create a namespace within a serverless Pinecone index.
Delete IndexTool to permanently delete a Pinecone index.
Delete NamespaceTool to permanently delete a namespace from a serverless index.
Describe BackupTool to retrieve detailed information about a specific backup.
Describe Bulk ImportTool to describe a specific bulk import operation in Pinecone.
Describe Index StatsTool to get index statistics including vector count per namespace, dimensions, and fullness.
Describe Restore JobTool to get detailed information about a specific restore job in Pinecone.
Generate EmbeddingsTool to generate vector embeddings for input text using Pinecone's hosted embedding models.
Get Model InformationTool to retrieve detailed information about a specific model hosted by Pinecone.
List Bulk ImportsTool to list all recent and ongoing bulk import operations in Pinecone.
List CollectionsTool to list all collections in a Pinecone project (pod-based indexes only).
List Index BackupsTool to list all backups for a specific Pinecone index.
List IndexesTool to list all indexes in a Pinecone project.
List Available ModelsTool to list all available embedding and reranking models hosted by Pinecone.
List NamespacesTool to list all namespaces in a serverless Pinecone index.
List Project BackupsTool to list all backups for indexes in a Pinecone project.
List Restore JobsTool to list all restore jobs for a project with pagination support.
List VectorsTool to list vector IDs in a Pinecone serverless index.
Query VectorsTool to perform semantic search within a Pinecone index using a query vector.
Rerank DocumentsTool to rerank documents by semantic relevance to a query.
Search Records in NamespaceTool to search records within a Pinecone namespace using text, vector, or ID query.
Start Bulk ImportTool to start an asynchronous bulk import of vectors from object storage (S3, GCS, or Azure Blob Storage) into a Pinecone index.
Update VectorTool to update a vector in Pinecone by ID.
Upsert Records to NamespaceTool to upsert text records into a Pinecone namespace.

Conclusion

You've successfully integrated Pinecone with Codex using Composio's Rube MCP server. Now you can interact with Pinecone directly from your terminal, VS Code, or the Codex App using natural language commands.

Key benefits of this setup:

  • Seamless integration across CLI, VS Code, and standalone app
  • Natural language commands for Pinecone operations
  • Managed authentication through Composio's Rube
  • Access to 20,000+ tools across 870+ apps for cross-app workflows
  • CodeAct workbench for complex tool chaining

Next steps:

  • Try asking Codex to perform various Pinecone operations
  • Explore cross-app workflows by connecting more toolkits
  • Build automation scripts that leverage Codex's AI capabilities

How to build Pinecone MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Pinecone MCP with OpenAI Agents SDK

Claude Agent SDK

Claude Agent SDK

Use Pinecone MCP with Claude Agent SDK

Google ADK

Google ADK

Use Pinecone MCP with Google ADK

LangChain

LangChain

Use Pinecone MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Pinecone MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Pinecone MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Pinecone MCP with LlamaIndex

CrewAI

CrewAI

Use Pinecone MCP with CrewAI

Claude Code

Claude Code

Use Pinecone MCP with Claude Code

FAQ

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 Codex?

Yes, you can. Codex 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.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free