Quberi MCP server

Quberi

Quberi is a multi-tenant AI knowledge base for teams. You upload documents, members ask questions in chat, and answers come from retrieved passages. Retrieval is filtered by what the asking user is allowed to see.

Permissions are per-document, not per-space. Within one space, two users can see different documents. A deny rule on a document wins over any allow rule or space role, retrieval is filtered inside the vector index, and rules are evaluated on every request, so a change applies to the next one.

Licensed under AGPL-3.0.

Run it yourself with Docker Compose (see Run it locally), or

use the hosted service at .

What it does

space grants access by organization, unit, position, group or individual member, each with a role. On top of that, any single document can be shared with someone who cannot read its space, or hidden from someone who can. Every question is checked against both.

• Permission-aware retrieval, per document. Documents live in spaces, and a

connected outside tools.

• Audit log. Sensitive actions are recorded, including searches made by

model, you can preview them, edit them, or drop individual passages.

• Send review. Before a question and the retrieved passages go to the chat

platform default. Chat uses OpenAI-compatible endpoints. Embeddings (BGE-M3) run inside the API and worker processes on CPU, not through a third-party API.

• Models. Bring your own key, use an organization-level model, or use a

be synced in.

• Agents. Build knowledge assistants and connect external agents (Coze, Dify).
• Sign-in and sync. Email code, Google or Feishu login. Feishu documents can

outside tools through OAuth (authorization code with PKCE). It is off by default. A plugin for DeepSeek Harness is published separately as dsh-quberi. An MCP server (listed in the official MCP Registry as com.quberi/mcp) exposes the same tools to Codex and other MCP clients — see docs/mcp-server.md for how to connect.

• Connected tools. An organization admin can allow read-only search from

member: it ends their web sessions, outside-tool access and Feishu sync, removes their private model keys, and freezes their personal space. See docs/member-offboarding.md.

• Member offboarding. The organization owner can deactivate a departing

Run it locally

Requirements: Docker with Compose, and pnpm if you want to work on the web app.

cp .env.example .env     # development values; change every secret before sharing
# Generate the required encryption key and put it in .env as QUBERI_ENCRYPTION_KEY:
python3 -c "import base64,os;print(base64.urlsafe_b64encode(os.urandom(32)).decode())"
make up                  # builds and starts the full stack

QUBERIENCRYPTIONKEY encrypts stored API keys and tokens. Keep it: if you lose it, stored credentials cannot be read again.

Then open . The API listens on .

The stack is Postgres, Redis, Qdrant, MinIO (via the community fork pgsty/silo), the API, a background worker and the web app. See deploy/README.md for details (it is written in Chinese).

Signing in locally

Real sign-in needs SMTP, Google or Feishu to be configured in .env. In a non-production environment (QUBERI_ENVIRONMENT=development, the default in .env.example), email verification codes are also written to the API log, so you can try the app without a mail server:

docker compose --env-file .env --profile app logs api | grep "DEV verification code"

Do not run with QUBERI_ENVIRONMENT=development on a machine that others can reach.

Platform admin console

Shortened. The full README is on GitHub.