verapli
Sign inJoin free
Menu

Guides · database · Everyday developer services

Qdrant Cloud

Managed Qdrant vector database. Create a cluster, then a database API key (shown once, default 90-day expiry).

Researched · not yet run liveLast researched 25 October 2026 · Qdrant · provider site

Researched, not yet run live. Built from the provider’s official pages (linked below). A person hasn’t walked this flow end to end yet, so check each step against the source.
Do this with verapliJSON for agents

Steps

Steps marked “human step” are ones only you can do: verapli never signs in, submits, pays or accepts terms for you.

  1. Sign in or create a Qdrant account

    Sign in to Qdrant. If you have no account yet, you create it yourself; verapli does not create accounts.

    • Guided by hand
    • Human step: You sign in

    Where: https://cloud.qdrant.io/

  2. Create a cluster

    Create a (free or paid) cluster in the Qdrant Cloud dashboard and note its URL.

    • Guided by hand
    • Human step: You press submit
    • After: Sign in or create a Qdrant account

    verapli captures QDRANT_URL here by plain code: encrypted in your browser, never shown to AI.

  3. Create a database API key

    On the cluster detail page open API Keys, click Create, name it and pick an expiry (default 90 days) and scope. Copy it now; it is shown only once.

    • Guided by hand
    • Human step: You press submit
    • After: Create a cluster

    verapli captures QDRANT_API_KEY here by plain code: encrypted in your browser, never shown to AI.

What you end up with

Env varSecretFormatWhat it is
QDRANT_URLnot secretQdrant cluster URL. Env var names are a verapli convention; the auth page names none.
QDRANT_API_KEYsecretQdrant database API key (api-key header)

Renewals

  • Qdrant database API key (if created with an expiry): every 90 days by default [1]

Pricing

  • Free tier: Single-node cluster, 0.5 vCPU, 1GB RAM, 4GB disk, no high availability.

Source [2]

For agents

The same entry as JSON: /api/v1/entries/qdrant/cloud · requirements /api/v1/requirements/qdrant/cloud · terms /api/v1/terms/qdrant/cloud.

Remote MCP (read-only, no auth)
claude mcp add --transport http verapli https://verapli.com/mcp

> "What do I need for Qdrant Cloud, and how long will it take?"
  → tools/call requirements { "provider_id": "qdrant/cloud" }

Sources

  1. Qdrant Cloud docs - Authentication Cluster Detail page > API Keys > Create; name and expiration (default 90 days, empty = none); read-only or collection scoping; shown only once; api-key header or Bearer · accessed 25 October 2026 · official
  2. Qdrant pricing Free tier single node 0.5 vCPU, 1GB RAM, 4GB disk, no high availability · accessed 25 October 2026 · official

Provider rules change. This page is generated from verapli registry version 2026.1025.316; spotted something out of date? Tell us. Qdrant is not affiliated with verapli.