Connect Pinecone to Claude Code

Manage Pinecone indexes, query and write vectors and records, and embed or rerank text with Pinecone's hosted models. Add Toolspoke to Claude Code once and it can use 18 Pinecone actions. Your Pinecone credential stays in Toolspoke, and you choose which actions Claude Code may call.

Set it up in Claude Code

Three steps, the first one once for every toolkit you will ever add.

  1. Add Toolspoke to Claude Code

    Run it in your project, then /mcp to sign in

    claude mcp add --transport http toolspoke https://toolspoke.com/mcp

    The sign-in opens in your browser, and Toolspoke asks you to approve it.

  2. Install Pinecone and connect it

    Add Pinecone to a project in your Toolspoke workspace.

    API key. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

    API key
    Pinecone console → choose the project → API keys → Create API key. A key reaches only the project that issued it. Give it All permissions for writes, or ReadOnly to use only the reads here.
  3. Choose what Claude Code may do

    All 18 actions start on. Switch off any of the 7 actions that change something in Pinecone, and Claude Code gets a refusal if it tries.

What you can ask Claude Code for

A few of the Pinecone actions that only read, so they are safe to try first.

  • Read one index's configuration, status and host
  • List the embedding and reranking models Pinecone hosts, with their dimensions and limits
  • Count the vectors in an index, per namespace, and report its dimension and fullness
  • List the namespaces in an index with their record counts

What Claude Code can do in Pinecone

11 actions read, 4 write and 3 delete or permanently change something.

Reads

  • List indexes

    List every index in the project with its dimension, metric, embedding model (for integrated indexes) and `host`. The host is what every vector and record action takes as index_host.

  • Describe index

    Read one index's configuration, status and host. For an index with integrated embedding, `embed.field_map` names the record field that holds the text.

  • List models

    List the embedding and reranking models Pinecone hosts, with their dimensions and limits.

  • Describe index stats

    Count the vectors in an index, per namespace, and report its dimension and fullness. Use it to find which namespaces exist.

  • List namespaces

    List the namespaces in an index with their record counts.

  • Query vectors

    Find the nearest vectors to a query vector, or to a stored vector by id. The vector must come from the same model the index was built with; for integrated indexes, search_records takes text instead.

  • Search records

    Search an index with integrated embedding by text. Pinecone embeds the query with the index's own model, and can rerank the hits.

  • Fetch vectors

    Read vectors by id, with their values and metadata.

  • List vector ids

    List vector ids in a namespace, optionally only those starting with a prefix. Serverless indexes only.

  • Embed

    Turn text into vectors with one of Pinecone's hosted embedding models. Stores nothing.

  • Rerank

    Order documents by relevance to a query with a hosted reranking model. Stores nothing.

Writes

  • Create index for model

    Create a serverless index with integrated embedding, so records are embedded by Pinecone on upsert and searched by text. `embed.field_map.text` names the record field that holds the text.

  • Configure index

    Change an index's deletion protection or tags.

  • Upsert vectors

    Write vectors, replacing any with the same id. Each needs an id and values of the index's dimension; metadata is optional.

  • Update vector

    Change one vector's values, or set metadata keys on it. Keys not named are left as they are.

Deletes or permanently changes

  • Delete vectors

    Delete vectors by id, by metadata filter, or every vector in a namespace. There is no undo.

  • Delete namespace

    Delete a namespace and every record in it. There is no undo. Serverless indexes only.

  • Delete index

    Delete an index and all its data. There is no undo, and Pinecone refuses while deletion protection is on.

Pinecone in Claude Code: questions

Does Claude Code see my Pinecone credential?

No. The credential is stored encrypted in Toolspoke, and the gateway adds it to each call. Claude Code only ever talks to Toolspoke, and the dashboard shows the last four characters of the credential and nothing more.

Can I stop Claude Code from changing things in Pinecone?

Yes. Each of the 18 actions can be switched off for a project. Turn off the 7 that change something and Claude Code can only read.

Will 18 actions crowd Claude Code's context?

No. Toolspoke shows Claude Code five bridge tools, plus a guide where a toolkit has one, and Claude Code searches for the Pinecone action it needs when it needs it. Adding more toolkits does not add more tools to its list.

Can I add it once for every project?

Yes. Add --scope user to the command and Claude Code keeps Toolspoke in every project on this machine. Without it, the server is added to the project you ran the command in.

What does it cost?

Tool calls are free on every plan, and a Pinecone call does not run in a sandbox, so it bills nothing.

Try Pinecone in Claude Code

Free to start, and tool calls cost nothing on any plan.