Qdrant RBAC MCP Server

Role-based access to your Qdrant vector store, via MCP. OIDC in, scoped JWTs out.

Local serverstreamable-http

What is the Qdrant RBAC MCP Server?

Qdrant RBAC is an MCP integration. Role-based access to your Qdrant vector store, via MCP. OIDC in, scoped JWTs out.

Packages and local setup

The published oci package is ghcr.io/fidonis/qdrant-mcp-rbac:0.4.0. Its declared MCP transport is streamable-http.

The package declares OIDC_ISSUER_URL (required): OIDC issuer / realm URL, e.g. https://kc.example.com/realms/myrealm; OIDC_AUDIENCE (required): Expected aud claim of incoming access tokens, e.g. mcp-server; QDRANT_URL (required): Qdrant HTTP endpoint, e.g. http://qdrant:6333; QDRANT_JWT_SECRET (required): HS256 signing secret, at least 32 bytes; must equal Qdrant's service.api_key.

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.4.0 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related vector search & rag MCP servers for tools that cover the same kind of work.

Configuration

VariableDescriptionRequired
OIDC_ISSUER_URLOIDC issuer / realm URL, e.g. https://kc.example.com/realms/myrealmYes
OIDC_AUDIENCEExpected aud claim of incoming access tokens, e.g. mcp-serverYes
QDRANT_URLQdrant HTTP endpoint, e.g. http://qdrant:6333Yes
QDRANT_JWT_SECRETHS256 signing secret, at least 32 bytes; must equal Qdrant's service.api_keyYes