How do I authenticate to Quelvio?
There is no API key. The first time you invoke a tool, your client redirects you to your organization’s Clerk‑hosted sign‑in page. After signing in, the client reuses the OAuth token (valid ~30 days).

@Quelvio
基本信息
Your company's brain for AI agents. MCP server for Quelvio enterprise knowledge platform.
使用下面的配置,将此服务器添加到你的 MCP 客户端。
{
"mcpServers": {
"quelvio": {
"url": "https://mcp.quelvio.com/http",
"transport": "streamable-http",
"auth": "oauth2"
}
}
}Search the company's connected knowledge across every source — Drive, SharePoint, Confluence, Slack, Notion — with cited synthesized answers, lifecycle awareness, and refusal-on-weak-context. Returns a written answer with [n] citations plus the ranked source chunks. Modes: `fast` (1,500 kT — retrieval-only, no synthesis), `standard` (12,500 kT — default; synthesized answer over the top retrieval set), `deep` (25,000 kT — wider retrieval + premium synthesis for complex questions). Pick the cheapest tier that answers the question. Responses are capped at 25,000 output tokens per Claude Connectors policy; if truncated, structured metadata carries `truncated: true` and `query_id` so the agent can call `get_source_detail` for full provenance.
List the taxonomy domains the company has indexed — with document counts, expert counts, and coverage levels — so an agent can decide whether to query before spending a Knowledge Token. Returns one row per domain with the canonical `taxonomy_domain` slug, document/chunk counts, expert count, coverage level (expert | partial | none), the single_expert risk flag, and the top contributor by authority. Use the slug as the `domain` filter on a follow-up `query_knowledge` call. Zero Knowledge Tokens consumed.
Return per-chunk source provenance for a previous query — document path, lifecycle state, embedding timestamp, contributor, last-updated — useful for verifying a citation or surfacing trust signals to a downstream system. Pass a `query_id` returned by an earlier `query_knowledge` call. Returns 404 if the query_id is unknown OR belongs to a different tenant (indistinguishable to prevent info-leak). Zero Knowledge Tokens consumed.
Quelvio is an MCP server that lets you search your company’s connected knowledge (from Drive, SharePoint, Confluence, Slack, Notion) directly from any AI tool supporting the Model Context Protocol. It is built for enterprise teams who want to query internal documents and conversations through assistants like Claude Desktop, Cursor, or VS Code Copilot.
Add the server’s URL (https://mcp.quelvio.com/http) to your MCP client’s configuration (JSON file or CLI). On first tool call, your browser opens your organization’s OAuth sign-in page; after signing in, the client resumes automatically. No API key is needed.
fast, standard, deep.list_domains.get_source_detail.There is no API key. The first time you invoke a tool, your client redirects you to your organization’s Clerk‑hosted sign‑in page. After signing in, the client reuses the OAuth token (valid ~30 days).
Every query is scoped to your individual identity. The server enforces tenant isolation, role‑based feature access (Owner/Admin/Member), and source‑system ACLs (e.g., Google Drive shares, SharePoint groups). You only see what your account would see in those source systems.
Tool calls consume Knowledge Tokens (kT): `list_domains` and `get_source_detail` are free; `query_knowledge` costs 1,500 kT (fast), 12,500 kT (standard), or 25,000 kT (deep). These rates are locked at the v0.9 release.
Yes. The server runs on Cloudflare Workers. Use `wrangler` to deploy with a `TOKEN_ENCRYPTION_KEY` and `CLERK_SIGN_IN_URL` secret. All OAuth artifacts live in Workers KV.
It uses Streamable HTTP (MCP spec 2025‑03‑26). For older clients that don’t support this transport, a stdio bridge is available via the npm package `@quelvio/mcp-server`.
Person-owned, portable AI memory served over MCP. Your knowledge, preferences, and decisions — captured in one assistant, available in all of them.
Local MCP server and CLI that keeps a Git-versioned, model-written index of a codebase and its database schema, so coding agents start each task with the whole system in view.

MCP connector for Snipara, the Project Brain for AI coding agents

Exact, shared memory for AI agents: a hierarchical database where totals always add up, every write is attributed to the agent and person behind it, and any figure traces back to its source file. Agents create databases,

AI agents start every session with amnesia — you re-explain the project, repeat your preferences, and correct the same mistakes over and over. PLUR gives them a memory that persists. Your agent's corrections, preference
评论