Connect Qdrant to Claude Code

Search, read and write points in Qdrant vector collections, and manage the collections and their payload indexes. Add Toolspoke to Claude Code once and it can use 15 Qdrant actions. Your Qdrant 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 Qdrant and connect it

    Add Qdrant 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.

    Cluster URL
    Qdrant Cloud → Clusters → your cluster → the Endpoint shown on its overview, with :6333 at the end. A self-hosted server is usually http://host:6333 and must be reachable from the internet. No path.
    API key
    Qdrant Cloud → Clusters → your cluster → API Keys → Create. A read-only key is enough for every read here; writes need a read-write key. Self-hosted: the service.api_key (or read_only_api_key) from the server's config.
  3. Choose what Claude Code may do

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

What you can ask Claude Code for

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

  • List the names of every collection on the cluster
  • Check whether a collection exists, without reading its configuration
  • List every collection alias on the cluster and the collection each one points to
  • Page through a collection's points in id order, optionally filtered by payload

What Claude Code can do in Qdrant

9 actions read, 4 write and 2 delete or permanently change something.

Reads

  • List collections

    List the names of every collection on the cluster. Call this first to confirm the connection and find what to query.

  • Get collection

    Read one collection's status, point count, vector configuration (size, distance, named vectors), payload indexes and optimizer state. Check the vector names and sizes here before querying.

  • Collection exists

    Check whether a collection exists, without reading its configuration.

  • List aliases

    List every collection alias on the cluster and the collection each one points to.

  • Query points

    Search a collection with Qdrant's universal query: nearest neighbours to a vector, recommendation from point ids, or an ordered or filtered listing. Pass `query` as a vector (a list of floats) for similarity search, or as a point id to search near that point. Qdrant does not embed text here, the vector must come from the same model the collection was built with.

  • Scroll points

    Page through a collection's points in id order, optionally filtered by payload. Returns next_page_offset; pass it back as `offset` for the next page.

  • Count points

    Count the points in a collection, or the ones matching a payload filter.

  • Get points

    Read specific points by id, with their payloads.

  • Facet

    Count how many points have each value of one payload key, like a GROUP BY. The key needs a keyword or integer payload index.

Writes

  • Create collection

    Create a collection. `vectors` sets the vector size and distance, either one unnamed vector or a map of named ones. Fails if the name is taken.

  • Create payload index

    Index one payload key so filters and facets on it are fast. Needed for facet and for order_by in scroll_points.

  • Upsert points

    Insert points, or replace points with the same id. Each point needs an id and a vector of the collection's size; the payload is optional JSON. Waits until the write is applied.

  • Set payload

    Add or overwrite payload keys on points chosen by id or by filter. Keys not named are left as they are.

Deletes or permanently changes

  • Delete points

    Delete points by id, or every point matching a filter. There is no undo. Give exactly one of points or filter.

  • Delete collection

    Delete a collection and every point in it. There is no undo short of restoring a snapshot.

Qdrant in Claude Code: questions

Does Claude Code see my Qdrant 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 Qdrant?

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

Will 15 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 Qdrant 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 Qdrant call does not run in a sandbox, so it bills nothing.

Try Qdrant in Claude Code

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