Can I use Qdrant as a CLI?

Yes. KosmoKrator exposes a Qdrant CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Qdrant through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Qdrant tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Qdrant credentials stored?

Qdrant credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Qdrant MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

database

Qdrant MCP Integration for Vercel AI SDK

Connect Qdrant to Vercel AI SDK through the local KosmoKrator MCP gateway with scoped tools, credentials, and write policy.

6 functions 4 read 2 write API key auth

Submit Qdrant feedback View package source

Connect Qdrant to Vercel AI SDK

Use KosmoKrator as a local integration gateway for Vercel AI SDK agents and scripts.

Create an MCP client that starts or connects to the KosmoKrator gateway for the selected integration. The gateway is local, scoped to this integration, and starts with --write=deny so Vercel AI SDK can inspect read-capable tools without receiving write access by default.

Qdrant MCP Config for Vercel AI SDK

Prefer CLI JSON calls when a workflow only needs one deterministic integration operation.

{
  "mcpServers": {
    "kosmokrator-qdrant": {
      "type": "stdio",
      "command": "kosmo",
      "args": [
        "mcp:serve",
        "--integration=qdrant",
        "--write=deny"
      ]
    }
  }
}

Run the Gateway Manually

kosmokrator mcp:serve --integration=qdrant --write=deny

Why Use KosmoKrator Here

Scoped tools

Expose only Qdrant instead of a broad multi-service tool list.

Local credentials

Reuse credentials already configured for the KosmoKrator CLI and Lua runtime.

Write policy

Start read-only, then opt into ask or allow for trusted workspaces.

Qdrant Tools Visible to Vercel AI SDK

Vercel AI SDK sees stable MCP tool names generated from the Qdrant integration catalog.

MCP tool	Source function	Type	Description
`integration__qdrant__qdrant_list_collections`	`qdrant.qdrant_list_collections`	Read	List all vector collections in the Qdrant cluster. Returns collection names and basic metadata.
`integration__qdrant__qdrant_get_collection`	`qdrant.qdrant_get_collection`	Read	Get detailed information about a specific Qdrant collection, including vector configuration, index status, and point count.
`integration__qdrant__qdrant_create_collection`	`qdrant.qdrant_create_collection`	Write	Create a new vector collection in Qdrant. You must specify the vector configuration (size, distance metric). Optionally provide HNSW, quantization, and optimization settings.
`integration__qdrant__qdrant_search`	`qdrant.qdrant_search`	Read	Search for the closest vectors in a Qdrant collection. Supports vector similarity search with optional filtering, payload selection, and scoring.
`integration__qdrant__qdrant_upsert_points`	`qdrant.qdrant_upsert_points`	Write	Insert or update points (vectors with optional payloads) in a Qdrant collection. Each point requires an ID and a vector. Payloads are optional metadata.
`integration__qdrant__qdrant_get_current_user`	`qdrant.qdrant_get_current_user`	Read	Get information about the Qdrant cluster, including cluster status, node information, and the authenticated user context.

Related Qdrant Pages

Qdrant CLIUse direct JSON commands instead of MCP discovery. Qdrant MCPFull gateway reference and MCP tool names. KosmoKrator for Vercel AI SDKClient-level gateway setup.