How to integrate Pinecone MCP with OpenCode

Trusted by teams at
AWS
Glean
Zoom
Airtable
GET STARTED FOR FREEGET A DEMO

30 min · no commitment · see it on your stack

Pinecone logo
OpenCode logo
divider

How to integrate Pinecone MCP with OpenCode

This guide explains how to connect Pinecone MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.

There are two ways to set this up:

Also integrate Pinecone with

Why use Composio?

Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:

  • Connect to 1,000+ apps with on-demand tool loading, so you do not fill your LLM context window with unnecessary tool definitions.
  • Use programmatic tool calling through a remote Bash tool, letting LLMs write their own code to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Handle large tool responses outside the LLM context to keep conversations lean.

Connect Pinecone with OpenCode

Option 1: Using Composio CLI

1. Install Composio CLI

Install the Composio CLI, authenticate, and initialize your project:

bash
# Install the Composio CLI
curl -fsSL https://composio.dev/install | bash

# Authenticate with Composio
composio login

During login, you will be redirected to the sign-in page. Finish the flow and you are all set.

Composio CLI authorization screen

2. Authorize Pinecone

Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:

  1. Launch OpenCode.
  2. Prompt it to "Authenticate with Pinecone Composio".
  3. Complete the authentication and authorization flow, and your Pinecone integration is all set.
  4. Start asking anything you want.

Option 2: Using Composio MCP

You can also connect Pinecone to OpenCode by adding Composio as an MCP server through the OpenCode CLI.

1. Add the Composio MCP server

bash
opencode mcp add

This launches an interactive prompt.

2. Fill in the fields

FieldValue
Namecomposio
Typeremote
URLhttps://connect.composio.dev/mcp
Require OAuthYes
Have client IDNo
OpenCode MCP server interactive prompt for Composio

Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.

Open your global OpenCode config:

bash
open ~/.config/opencode/opencode.json

Add this under the mcp key and save the file.

bash
{
  "mcp": {
    "composio": {
      "type": "remote",
      "url": "https://connect.composio.dev/mcp",
      "enabled": true
    }
  }
}

3. Authenticate

Authenticate the Composio MCP server you just added:

bash
opencode mcp auth composio

This opens a browser session. Authorize Composio and you are done.

Composio browser authorization for OpenCode MCP

4. Verify installation

bash
opencode mcp list

5. Connect Pinecone with OpenCode

Now, in the chat, ask the agent to connect to Pinecone or give it any Pinecone-related task.

For example, ask it to:

  • "Query all vectors similar to user question"
  • "Upsert document embeddings into a namespace"
  • "Delete vectors from the archive index"

It will prompt you to authenticate and authorize access to Pinecone.

That is it. Composio tools are now available in OpenCode, and your Pinecone account is ready to use.

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.

Way Forward

Now that Pinecone is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.

Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.

How to build Pinecone MCP Agent with another framework

ChatGPT logo

ChatGPT

Use Pinecone MCP with ChatGPT

OpenAI Agents SDK logo

OpenAI Agents SDK

Use Pinecone MCP with OpenAI Agents SDK

Claude Agent SDK logo

Claude Agent SDK

Use Pinecone MCP with Claude Agent SDK

Claude Code logo

Claude Code

Use Pinecone MCP with Claude Code

Claude Cowork logo

Claude Cowork

Use Pinecone MCP with Claude Cowork

Codex logo

Codex

Use Pinecone MCP with Codex

Cursor logo

Cursor

Use Pinecone MCP with Cursor

OpenClaw logo

OpenClaw

Use Pinecone MCP with OpenClaw

Hermes logo

Hermes

Use Pinecone MCP with Hermes

CLI logo

CLI

Use Pinecone MCP with CLI

Google ADK logo

Google ADK

Use Pinecone MCP with Google ADK

LangChain logo

LangChain

Use Pinecone MCP with LangChain

Vercel AI SDK logo

Vercel AI SDK

Use Pinecone MCP with Vercel AI SDK

Mastra AI logo

Mastra AI

Use Pinecone MCP with Mastra AI

LlamaIndex logo

LlamaIndex

Use Pinecone MCP with LlamaIndex

CrewAI logo

CrewAI

Use Pinecone MCP with CrewAI

VS Code logo

VS Code

Use Pinecone MCP with VS 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 OpenCode?

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

Get started for freeGet a demo↗