Database
Pinecone MCP connector
The Pinecone connector links your Pinecone indexes, vectors, records, collections and imports to Claude, ChatGPT, Cursor and any MCP client through one governed endpoint, so people can search, inspect and tidy them by asking in plain language.
-
How it connects. Connects with an API key. The credential goes into a vault nobody reads back.
-
One address. https://api.elaichi.ai/mcp, the same for every user.
-
Their own access. An agent never gets more than the person it acts for.
47 tools
How to connect
How to connect Pinecone to Claude, ChatGPT or Cursor
Two steps, about a minute.
In Elaichi
Connect Pinecone once
-
Open Connections, choose Add connection, and pick Pinecone.
-
Optionally set Share with to give a team access, then press Connect.
-
Paste a Pinecone API key. One person generates a token in Pinecone and pastes it once. Everyone else works through Share with, and never sees it.
The credential is vaulted. Nobody reads it back, not even the AI.
Add connection
Choose a connector.
In your AI client
Point it at one endpoint
Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.
Connect Pinecone to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect Pinecone to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect Pinecone to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Connect Pinecone to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
Use cases
What teams do with Pinecone through Elaichi
Every one of these runs inside the access the person already has, and lands in the same audit log.
-
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.”
AI tools
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.
No tools match your search.
See it in Elaichi
What connecting Pinecone gets you
6 screens from the product, each doing one job for your Pinecone account.
The agent
Ask about Pinecone indexes in plain language.
Answers come from live Pinecone indexes, namespaces and vectors, not a stale export.
- indexes
- vectors
- namespaces
- imports
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 or Cursor
MCP clients
Claude, ChatGPT and Cursor share one endpoint.
Connect any MCP client to Pinecone over OAuth, no SDK, no shared API key.
ElaichiMCP clientsClaude
ChatGPT
Cursor
Copy the endpoint
Tool catalog
47 Pinecone tools are ready to call.
Indexes, vectors, imports and index stats are covered without writing custom code.
- Get single Pinecone index by ID
- Create a Pinecone index
- List all Pinecone indexes
- Update a Pinecone index by ID
ElaichiToolsToolboxes
Every team gets its own Pinecone toolbox.
Curate one toolbox per team so each group sees only relevant Pinecone tools.
- Search
- Data engineering
- Machine learning
- Platform
ElaichiToolboxesShared connections
Teammates query Pinecone without touching a key.
See who connected each Pinecone account and how many teams and members use it.
- Search production
- Search staging
- Data engineering
- Machine learning
ElaichiConnectionsAudit log
Every Pinecone call is written down.
When, who, what happened, type and resource for each index and vector call.
- When
- Who
- What happened
- Type
ElaichiAudit logLaunching soon
From answering questions to doing the work
A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.
Automations
A schedule fires, Pinecone work gets done.
Fetch vectors, group them, draft a digest, get approval, post back to Pinecone.
Pinecone digest
Run 418 · started 2 minutes ago · on behalf of Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch indexes
Pinecone
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
Post the digest
Pinecone
Queued
Collections and dashboards
Pinecone index health, counted not guessed.
Four metrics, 14 days of vectors created and a team breakdown, refreshed on schedule.
Pinecone health
Refreshed 4 minutes ago · every 15 minutes · from the indexes collection
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%
Related connectors
More from the catalog
FAQ
Frequently asked questions
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, 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 hiding 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 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 blocking deleting an index, removing vectors or deleting a collection. A blocked action is never shown to Claude, ChatGPT, Cursor or any other client at all, so no prompt, accidental or otherwise, can trigger it.
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 and every other connected client.
Put Pinecone in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.