Your company's brain, exposed as a tool any AI agent can call.

Install

Three install paths — same server, different clients.

Claude Desktop · Claude Connectors

Open Settings → Integrations → Add server. Paste:

Claude walks you through OAuth sign-in with your Quelvio workspace credentials. The integration auto-binds to your employee identity — the same one used for the dashboard.

Cursor

Paste into ~/.cursor/mcp.json (or via Cursor settings UI):

{
  "mcpServers": {
    "quelvio": {
      "url": "https://mcp.quelvio.com/http"
    }
  }
}

Cursor's first call triggers the OAuth flow in a browser tab.

Any other MCP client

• Server URL: https://mcp.quelvio.com/http
• Authentication: OAuth 2.1 with PKCE; DCR-supported
• Registry entry: com.quelvio/mcp-server on registry.modelcontextprotocol.io

Tools

Three tools. The first is the workhorse; the other two are zero-cost helpers.

We deploy the payments service via ECS rolling updates [1]. Releases
are cut by tagging the main branch — the backend-deploy workflow
applies migrations to RDS, registers a new task def, and rolls the
service [2]. Pre-deploy checklist lives at [3].

Sources:
  [1] runbooks/payments-service-deploy.md (Confluence) — Senior Platform Eng, 2 days ago
  [2] .github/workflows/backend-deploy.yml (GitHub) — Platform Team, 5 days ago
  [3] checklists/pre-deploy.md (Confluence) — Senior Platform Eng, 2 weeks ago

{
  "query_id": "<query-id>",
  "coverage": "expert",
  "retrieval_mode": "hybrid",
  "tokens_consumed": 12500,
  "latency_ms": 1180
}

Modes

Knowledge Tokens are Quelvio's unit of work. Each mode has a fixed kT cost — no surprise charges from variable token usage.

Your daily kT pool depends on your plan. See /pricing for plan-specific pool sizes. The pool resets at 00:00 UTC.

Plans bill per seat — kT pools come with each seat. See /pricing for plan details.

Authentication & identity

Every query is scoped to your individual employee identity, not just your tenant. The MCP server records the per-employee identity on each call so cross-employee provenance inspection is automatic — Owner/Admin can audit, members can't snoop on each other.

OAuth 2.1 with PKCE is required (the MCP spec mandates it). The Quelvio MCP server also supports Dynamic Client Registration (RFC 7591), so MCP-aware clients like Claude Desktop register themselves on first connect — no operator pre-provisioning.

Sign-in uses your workspace's identity provider — the same one used for the dashboard at enterprise.quelvio.com. When configured, this federates to your SAML, Google Workspace, or Microsoft Entra provider. Access tokens are stored encrypted (AES-GCM) in Cloudflare KV on the MCP server — never on the client's filesystem. Token rotation and revocation happen server-side via the /oauth/revoke endpoint; admins can revoke active tokens from the dashboard.

Permission model

Three layers, all enforced server-side:

1. Tenant isolation. Content is stored in per-tenant collections; cross-tenant content is structurally unreachable, not just policy-gated.
2. Role-based feature access. Owner / Admin / Member determines which calls succeed. get_source_detail is scoped to your own queries by default — only Owner/Admin can inspect another member's queries.
3. Source permission filtering. permission_emails on every chunk, resolved at ingest time from each source's ACLs (Drive shares, SharePoint groups, Confluence space restrictions). MCP queries see only what your individual account would see in the source system. There is no flag, env var, or dashboard toggle that disables this filter.

Response caps & truncation

Per Claude Connectors policy, every tool response is capped at 25,000 output tokens. The MCP server enforces this deterministically:

• Clamp excerpts to 200 chars
• Drop lowest-rank sources (preserving ≥3)
• Truncate the synthesis body

Truncation is signaled via truncated: true in the structured metadata block, alongside the query_id so the agent can call get_source_detail for full provenance on any source it wants to inspect deeper.

Streaming

When a client sends Accept: text/event-stream and mode is standard or deep, the MCP server proxies Quelvio's SSE pipeline — the synthesized answer streams token-by-token from the model to the MCP server. The MCP response itself is still a single JSON body (most MCP clients today expect that); native per-token streaming to the client lands when the spec adds output deltas.

fast never streams — it has no synthesis body to incrementally produce.

Cost transparency

Every query_knowledge response includes tokens_consumed in the structured metadata block. Your tenant's daily pool state, current period's billable usage, and projected next invoice live on the billing dashboard at enterprise.quelvio.com/billing.

Links & references