qdrant

Manage Qdrant vector database collections, points, filters, and snapshots via REST API.

55|4|Updated Feb 5, 2026
One-click install
npx skills add https://github.com/bug-ops/zeph --skill qdrant-bug-ops
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qdrant
Source: https://github.com/bug-ops/zeph/tree/main/.zeph/skills/qdrant
Command: npx skills add https://github.com/bug-ops/zeph --skill qdrant-bug-ops

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Managing and querying a Qdrant vector database over REST can be complex without a unified interface. This skill provides a centralized way to perform collection CRUD, vector upserts, searches, and operational tasks like snapshots and cluster status through simple REST calls.

Core Features & Use Cases

  • Create, delete, and inspect collections to organize your embeddings.
  • Upsert points with vectors and payloads, and perform similarity searches with optional payload filtering.
  • Apply advanced filters (must, should, must_not) and payload indexes to refine results; support for named vectors and multi-vector queries.
  • Manage snapshots, aliases, and cluster health to keep production deployments reliable.
  • Use Case: build a scalable semantic search service that stores embeddings in Qdrant and serves accurate results at scale.

Quick Start

Connect to your Qdrant instance at http://localhost:6333 (override with QDRANT_URL) and begin issuing REST API calls to manage collections, points, filters, and snapshots.

Frequently Asked Questions about qdrant

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I manage Qdrant vector database collections via REST API?

You can perform collection CRUD operations on a Qdrant vector database by issuing REST API calls to create, delete, and inspect collections to organize your embeddings.

How do I upsert points and perform similarity searches with filters in Qdrant?

To upsert points with vectors and payloads in Qdrant, use REST calls to perform similarity searches with optional payload filtering, applying advanced filters like must, should, and must_not to refine results.

Do I need a running Qdrant instance to use this REST API management skill?

Yes, this skill requires a running Qdrant instance accessible by default at http://localhost:6333, which you can override using the QDRANT_URL environment variable, along with curl installed.

Can I manage snapshots and check cluster health for Qdrant collections?

Yes, you can manage snapshots, aliases, and monitor cluster health for Qdrant collections through REST API calls to keep production deployments reliable and maintain operational stability.

Does Qdrant REST API support named vectors and multi-vector queries?

Yes, the Qdrant REST API supports named vectors and multi-vector queries, allowing you to apply payload indexes to refine results and build a scalable semantic search service.

What is the best way to build a scalable semantic search service with Qdrant?

The best way to build a scalable semantic search service is to store embeddings in Qdrant and use REST API calls to manage collections, upsert points, and serve accurate filtered similarity searches at scale.