Skip to main content

​
At a glance

  • Availability: Experimental (how to enable).
  • Authentication: API key.
  • Connection: The key from QDRANT_API_KEY is sent as the api-key header.
  • Provider documentation: Authentication reference.

​
Credentials

Set these per environment. See Connect an integration.

​
Setup

  1. Create a Qdrant Cloud account: Sign up at https://cloud.qdrant.io. The free tier includes a 1GB cluster, enough for testing. Self-hosted Qdrant requires an API key plus native TLS or an HTTPS reverse proxy before you use this connector.
  2. Create a cluster and API key: Create a cluster, then open its API Keys tab and create a database API key. Copy it immediately: it is only shown once.
  3. Store the key and note your endpoint: Add QDRANT_API_KEY=… to your .env file. Copy the cluster endpoint hostname from Cluster details; tools take it as the QDRANT_CLUSTER_HOST environment variable without scheme or port (e.g. xyz-example.eu-central-1-0.aws.cloud.qdrant.io); requests go to port 6333.
  4. Verify access: With QDRANT_CLUSTER_HOST configured, run the List Collections tool.

​
Provider notes

  • The API key is sent in the api-key header; Qdrant Cloud also accepts Authorization: Bearer
  • Every tool needs the QDRANT_CLUSTER_HOST environment variable (hostname only; requests target HTTPS port 6333); there is no global Qdrant API host
  • Self-hosted Qdrant must enable native TLS or use an HTTPS reverse proxy. The default HTTP listener on port 6333 is not supported by this connector
  • Migrating from earlier versions: tools no longer accept a clusterHost parameter; set QDRANT_CLUSTER_HOST once instead. Until it is configured, tools fail fast with ‘Set local integration host variables: QDRANT_CLUSTER_HOST’ and no request is sent
  • QDRANT_CLUSTER_HOST is treated as sensitive because the cluster hostname identifies your private deployment; the CLI masks it in prompts and output
  • Vectors must match the collection’s configured vector size; generate embeddings separately (e.g. with OpenAI or Mistral)
Provider API reference.

​
Tools

​
Verify the connection

Call a read tool such as qdrant__list_collections with arguments for your account. Confirm that the result comes from the intended account or workspace before enabling write tools.