MCP serverOfficial registry

Qdrant RBAC

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

by de.fidonisv0.4.0GitHub Website

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Local command

docker run -i --rm ghcr.io/fidonis/qdrant-mcp-rbac:0.4.0

Credentials from the publisher

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

Provider

Claude Code

OIDC_ISSUER_URL=<value> OIDC_AUDIENCE=<value> QDRANT_URL=<value> QDRANT_JWT_SECRET=<secret> claude mcp add de.fidonis-qdrant-mcp-rbac -- docker run -i --rm ghcr.io/fidonis/qdrant-mcp-rbac:0.4.0

Run in a terminal.

Claude Desktop

{
  "mcpServers": {
    "de.fidonis-qdrant-mcp-rbac": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/fidonis/qdrant-mcp-rbac:0.4.0"
      ],
      "env": {
        "OIDC_ISSUER_URL": "<value>",
        "OIDC_AUDIENCE": "<value>",
        "QDRANT_URL": "<value>",
        "QDRANT_JWT_SECRET": "<secret>"
      }
    }
  }
}

claude_desktop_config.json

Step-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Related MCP

Qdrant RBAC

Add this server

Host a copy with our keys and logs.

More like this

Firecrawl

Notion

Context7