Skip to content

Pinecone MCP connector

The Pinecone connector links your Pinecone indexes, vectors, records, collections and imports to Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client through one governed endpoint, so people can search, inspect and tidy them by asking in plain language.

  • Connects with an API key
  • Free 14-day trial
  • No credit card
Claude Elaichi connected

List all Pinecone indexes and their vector counts.

Working in Pinecone with Elaichi

  • Get single Pinecone index by ID
  • List all Pinecone indexes
  • Get single Pinecone vector by ID
Ask anything…
Governance / Audit log Last 24 hours
Pinecone Get single Pinecone vector by ID Emily Carter · Claude · 9:41 AM Done
Pinecone List all Pinecone indexes Emily Carter · Claude · 9:41 AM Done
Pinecone Get single Pinecone index by ID Emily Carter · Claude · 9:41 AM Done
Pinecone Create a Pinecone index Megan Brooks · ChatGPT · 9:38 AM Done
Pinecone Update a Pinecone index by ID Ryan Hayes · Cursor · 9:35 AM Done

How to connect Pinecone to Claude, ChatGPT, Cursor or Microsoft Copilot

Step by step, for each AI app

Pinecone MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Pinecone MCP connector for Claude Code

  1. 1

    In a terminal, run claude mcp add with the endpoint.

    https://api.elaichi.ai/mcp
  2. 2

    Start Claude Code and run /mcp.

  3. 3

    Pick elaichi, then sign in and approve in the browser.

Terminal

$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp

Use --scope project instead to share it with the repository through .mcp.json.

Pinecone MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

Pinecone MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Pinecone MCP connector for Microsoft Copilot

  1. 1

    In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.

  2. 2

    Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.

    https://api.elaichi.ai/mcp
  3. 3

    Create a new connection, sign in and approve, then press Add to agent.

  4. 4

    Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Server URL
https://api.elaichi.ai/mcp
Authentication
OAuth 2.0
Type
Dynamic discovery

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

Connect Pinecone to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

What teams do with Pinecone through Elaichi

Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Pinecone is logged.

  • Engineering

    Check an index before a release

    Ask how many vectors an index holds, which namespaces are filling up and whether the stats look right before shipping a change that depends on it.

  • Data

    Load a fresh batch of vectors

    Kick off an import from a prepared file, watch its progress and confirm it finished, without opening the Pinecone console or writing a script.

  • Product

    Test what a search returns

    Run a quick similarity search against a Pinecone index and read the top matches back, to judge whether the results feel right for a feature you are planning.

  • Support

    Find the record behind a bad answer

    When a customer reports an odd result, look up the exact record by ID, see what it contains and update or remove it on the spot.

  • Platform

    Snapshot an index into a collection

    Create a collection from a live index before a risky migration, and list existing collections to confirm the backup is there.

  • Operations

    Clear out indexes nobody uses

    List every Pinecone index in the project, spot the abandoned experiments and delete the ones that are only costing money.

Try asking

  • “List all Pinecone indexes and their vector counts.”
  • “Search the support-docs index for refund policy vectors.”
  • “Show index stats for the production Pinecone index.”

See all 47 Pinecone tools →

What connecting Pinecone gets you

6 screens from Elaichi, each doing one job for your Pinecone account.

Elaichi Agent

Ask Elaichi to work across your apps.

List all Pinecone indexes and their vector counts.

Search the support-docs index for refund policy vectors.

Show index stats for the production Pinecone index.

Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot

The agent

Ask about Pinecone indexes in plain language.

Answers come from live Pinecone indexes, namespaces and vectors, not a stale export.

ElaichiAI apps
Claude ChatGPT Cursor Microsoft Copilot

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

AI apps

Claude, ChatGPT, Cursor and Microsoft Copilot share one endpoint.

Connect any MCP client to Pinecone over OAuth, no SDK, no shared API key.

ElaichiTools
Tool Action Description
Get single Pinecone index by ID Get Get a specific Pinecone index by id. Returns the full index object including name, host, metric, dimension, spec, deletion_protection, and status. Required: id.
Create a Pinecone index Create Create a new Pinecone index for dense vectors, sparse vectors, or full-text search documents. Returns the created index object including name, host, and status. Required: name and spec (with cloud and region). Dense vector indexes also require dimension and metric; sparse vector indexes require metric set to dotproduct.
List all Pinecone indexes List List all Pinecone indexes in the current project. Returns an array of index objects including name, dimension, metric, host, and status for each.
Update a Pinecone index by ID Update Update configuration for a Pinecone index by id. Supports updating deletion_protection and tags. Required: id.
Delete a Pinecone index by ID Delete Delete a Pinecone index by id. Returns an empty response on success. Required: id.

Tool catalog

47 Pinecone tools are ready to call.

Indexes, vectors, imports and index stats are covered without writing custom code.

ElaichiToolboxes
Name Source template Tools Created

Search toolbox

Pinecone · indexes and vector search

Pinecone starter 18 Mar 4, 2026

Data engineering toolbox

Pinecone · imports and bulk vector loads

— 9 Mar 2, 2026

Machine learning toolbox

Pinecone · embeddings and index stats

— 24 Feb 27, 2026

Platform toolbox

Pinecone · index creation and configuration

Pinecone starter 6 Feb 19, 2026

Product analytics toolbox

Pinecone · namespaces and query volume

— 31 Jan 30, 2026

Support engineering toolbox

Pinecone · read-only vector lookups

— 12 Jan 22, 2026

Toolboxes

Every team gets its own Pinecone toolbox.

Curate one toolbox per team so each group sees only relevant Pinecone tools.

ElaichiConnections
Connection Scope Status Access
PI

Pinecone (Search production)

Connected by Emily Carter

Personal • Active 1 team · 6 members
PI

Pinecone (Search staging)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
PI

Pinecone (Data engineering)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
PI

Pinecone (Machine learning)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
PI

Pinecone (Platform)

Connected by Ryan Hayes

Personal • Active Not shared
PI

Pinecone (Analytics)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Shared connections

Teammates query Pinecone without touching a key.

See who connected each Pinecone account and how many teams and members use it.

ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

[email protected]

Pinecone Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

[email protected]

Pinecone Indexes Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

[email protected]

Pinecone Indexes List Toolbox

Audit log

Every Pinecone call is written down.

When, who, what happened, type and resource for each index and vector call.

From answering questions to doing the work

A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.

Pinecone digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch indexes

    Pinecone

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Jake Morgan

    Approve
  6. Post the digest

    Pinecone

    Queued

Automations

A schedule fires, Pinecone work gets done.

Fetch vectors, group them, draft a digest, get approval, post back to Pinecone.

Pinecone health

Refreshed 4 minutes ago · every 15 minutes · from the indexes collection

Live

Indexes

1,284 ↓ 12%

Vectors

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Indexes created

Last 14 days

By team

Share of activity

Search production 34%

Search staging 27%

Data engineering 21%

Machine learning 18%

Collections and dashboards

Pinecone index health, counted not guessed.

Four metrics, 14 days of vectors created and a team breakdown, refreshed on schedule.

For IT and engineering

Elaichi vs Zapier MCP vs Composio for Pinecone

All three can connect Pinecone to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Pinecone, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Pinecone tools Allow or restrict single Pinecone tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Pinecone call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price Free for one person; $15 per user per month on Gold. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

Pinecone tools for your AI agents

47 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pinecone, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

Questions, answered

How do I connect Pinecone to Claude?

Connect Pinecone in Elaichi first: paste a Pinecone API key from your Pinecone project into the connection form, and Elaichi confirms it works. There is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp as the endpoint. Sign in to Elaichi when Claude asks, and your Pinecone indexes and records are available in the conversation.

Does Pinecone work with ChatGPT and Cursor as well as Claude?

Yes. Once Pinecone is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Pinecone once and every client you use picks it up.

What can an AI agent actually do with my Pinecone data?

An agent connected to Pinecone can list your indexes and report their stats, run a similarity search and read back the matching vectors or records, look up a single vector or record by ID, and update or remove it. It can create indexes and collections, start a bulk import from a file and check whether an import has finished. Because Pinecone exposes a lot of actions, the agent looks up the right one for each request, so a short concrete ask such as "show stats for the product index" works better than a long paragraph.

Does connecting Pinecone give the AI access to every index in my project?

The AI can only reach what the Pinecone API key you connected can reach, so a key scoped to one project or one index limits the agent to exactly that. Elaichi can narrow that further, for example restricting the actions that delete indexes, but it can never grant anything the key itself does not allow. Each person still signs in to Elaichi as themselves, so every Pinecone call is tied to a named person.

Can my team share one Pinecone connection?

Yes. One person connects Pinecone with an API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles that key. Each teammate signs in to Elaichi as themselves, so the audit log records exactly who searched an index, who started an import and who removed a record.

Can I stop an agent from deleting or changing things in Pinecone?

Yes. Restrictions in Elaichi apply per action, so you can allow searching and reading Pinecone indexes and records while restricting deleting an index, removing vectors or deleting a collection. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot or any other client cannot run it, whatever the prompt says.

What happens to a Pinecone connection when someone leaves?

When you offboard a person in Elaichi, their access to Pinecone through every client ends immediately, and the Pinecone API key never traveled with them. A shared Pinecone connection keeps working for everyone else on the team. If you want to remove Pinecone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other connected client.

Does the Pinecone MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Pinecone is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Pinecone?

Yes. Both let Claude, ChatGPT or Cursor use Pinecone. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Pinecone call.

How is Elaichi different from Composio for Pinecone?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Pinecone: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Pinecone in front of your team

14 days of Black, no credit card. Connect it once and pick what each team can call.

When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.

Add one link to your AI app

The same link for everyone on your team.

https://api.elaichi.ai/mcp
  • ChatGPT
  • Claude
  • Cursor
  • Microsoft Copilot