What is the key difference between Qdrant RBAC and Celiums Memory?

Qdrant RBAC belongs to the Knowledge & Memory category with cloud HTTP/SSE execution, while Celiums Memory belongs to the Knowledge & Memory category with local stdio execution.

How do I install Qdrant RBAC or Celiums Memory in Claude Desktop or Cursor?

Copy the mcpServers JSON configuration snippet provided on this page into your claude_desktop_config.json or ~/.cursor/mcp.json file and restart your AI client.

Are Qdrant RBAC and Celiums Memory free or paid?

Qdrant RBAC operates under a Free / Open Source model (No auth required). Celiums Memory operates under a Free / Open Source model (API Key required).

Which MCP server has more tools and community activity?

Qdrant RBAC lists 8 tools with 0 views and 0 GitHub stars. Celiums Memory lists 6 tools with 2 views and 23 GitHub stars.

Can I use both Qdrant RBAC and Celiums Memory together in the same MCP host?

Yes! MCP hosts like Claude Desktop, Cursor, Windsurf, Cline, and VS Code support configuring multiple servers under the mcpServers object simultaneously.

Side-by-Side Model Context Protocol Comparison

Qdrant RBAC vs Celiums Memory

In-depth architectural comparison of the Qdrant RBAC and Celiums Memory MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.

At a Glance & Executive Verdict

Qdrant RBAC

Knowledge & Memory · Remote HTTP/SSE

Quality: 51/100 (Good) | Auth: No auth required

Celiums Memory

Knowledge & Memory · Local stdio

Quality: 53/100 (Good) | Auth: API Key required

Verdict Summary: Choose Qdrant RBAC if you need specialized Knowledge & Memory tools running via a hosted cloud SSE transport. Choose Celiums Memory if your workspace requires Knowledge & Memory integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.

Which MCP Server Should You Choose?

Choose Qdrant RBAC when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer remote streaming HTTP/SSE transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You have access to required keys: OIDC_ISSUER_URL, OIDC_AUDIENCE, QDRANT_URL, QDRANT_JWT_SECRET, RBAC_ADMIN_ROLE, RBAC_ACL_COLLECTION, OIDC_JWKS_CACHE_TTL.
Primary tools included: list_collections, get_collection_info, search_collection.

Explore Qdrant RBAC Details

Choose Celiums Memory when:

You need dedicated capabilities in the Knowledge & Memory domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: SQLITE_PATH, DATABASE_URL, QDRANT_URL, VALKEY_URL, CELIUMS_API_KEY, PORT, CELIUMS_LLM_API_KEY, CELIUMS_LLM_BASE_URL.

Feature & Specification Comparison

Specification	Q Qdrant RBAC Knowledge & Memory	Celiums Memory celiums Knowledge & Memory
Summary
Category & Scope	Knowledge & Memory	Knowledge & Memory
Quality signal

Tools & Capabilities Breakdown

Qdrant RBAC Tools (8)

list_collections

(any) — returns only collections the caller can read

get_collection_info

r` on the target collection

search_collection

r` on the target collection

search_collection_by_text

r` on the target collection

scroll_collection

r` on the target collection

list_documents

r` on the target collection

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

Qdrant RBAC Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "qdrant-rbac": {
      "url": "http://localhost:8000/mcp"
    }
  }
}

Celiums Memory Configuration

mcpServers (Claude Desktop / Cursor)

{
  "mcpServers": {
    "celiums-celiums-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@celiums/memory"
      ],
      "env": {
        "SQLITE_PATH": "YOUR_SQLITE_PATH_HERE",
        "DATABASE_URL": "YOUR_DATABASE_URL_HERE",
        "QDRANT_URL": "YOUR_QDRANT_URL_HERE",
        "VALKEY_URL": "YOUR_VALKEY_URL_HERE",
        "CELIUMS_API_KEY": "YOUR_CELIUMS_API_KEY_HERE",
        "PORT": "YOUR_PORT_HERE",
        "CELIUMS_LLM_API_KEY": "YOUR_CELIUMS_LLM_API_KEY_HERE",
        "CELIUMS_LLM_BASE_URL": "YOUR_CELIUMS_LLM_BASE_URL_HERE"
      }
    }
  }
}

Frequently Asked Questions

Qdrant RBAC is categorized under Knowledge & Memory and uses a remote streaming HTTP/SSE transport. In contrast, Celiums Memory belongs to Knowledge & Memory using local stdio subprocess. Select Qdrant RBAC when you need capabilities focused on knowledge & memory and Celiums Memory when you require tools for knowledge & memory.

More alternatives to Qdrant RBAC More alternatives to Celiums Memory Knowledge & Memory category hub Canonical compare URL

Qdrant RBAC vs Celiums Memory

At a Glance & Executive Verdict

Which MCP Server Should You Choose?

Choose Qdrant RBAC when:

Choose Celiums Memory when:

Feature & Specification Comparison

Tools & Capabilities Breakdown

Qdrant RBAC Tools (8)

Ready-to-Paste Client Configurations

Frequently Asked Questions

Related MCP Server Comparisons

Popular comparisons with Qdrant RBAC

Popular comparisons with Celiums Memory

Celiums Memory Tools (6)