Quelvio

Your company's brain for AI agents.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Query Knowledge: Search the company's connected knowledge across every source — Drive, SharePoint, Confluence, Slack, Notion — with cited synthesized answers, lifecycle awareness, and refusal-on-weak-
  • List Domains: 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.
  • Get Source Detail: Return per-chunk source provenance for a previous query — document path, lifecycle state, embedding timestamp, contributor, last-updated — useful for verifying a citation or surfaci

What data it sees

Do you need an account

No: the server works without sign-in

Your company's brain for AI agents.

Quelvio continuously understands your organization's knowledge across every connected system — what's authoritative, what's recent, what's persistent, what's temporary, and what should be forgotten. Returns cited answers grounded in your authoritative sources, refusing when the corpus doesn't actually answer the question.

What makes Quelvio different

  • Cross-document supersession — when sources conflict, surfaces the current truth and explicitly names what it supersedes
  • Authority-weighted retrieval — weights documents by who said them on the relevant topic
  • Refuses on weak context — when the corpus doesn't actually answer, says so. No hallucinated numbers, no fabricated citations
  • Cross-source synthesis — reasons across Slack, Confluence, Notion, Drive simultaneously with explicit source attribution
  • Lifecycle awareness — tracks current vs deprecated content, flags stale procedures

Tools

  • query_knowledge — search across all connected sources with optional synthesis modes (fast / standard / deep)
  • list_domains — discover what knowledge domains your tenant has indexed
  • get_source_detail — chunk-level provenance for any cited result

Setup

  1. Sign up at https://quelvio.com — 5GB indexed + 2 queries/day free tier
  2. Connect your sources (Google Drive, SharePoint, Confluence, Slack, Notion, GitHub)
  3. Add this MCP server to your client
  4. Complete OAuth on first tool call

Authentication

OAuth 2.1 with PKCE. Per-employee identity propagation — each query is scoped to the individual employee's permissions in source systems.

Pricing

Per Knowledge Token model. Paid plans scale with usage and seats.

How to connect

How to connect Quelvio to Claude

The server address to paste into Claude settings:

https://mcp-server--quelvio.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Quelvio to ChatGPT

The server address to paste into ChatGPT settings:

https://mcp-server--quelvio.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Quelvio to Cursor

The server address to paste into Cursor settings:

https://mcp-server--quelvio.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (3)

Raw names from tools/list. Only developers need these.

query_knowledgeSearch 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_domainsList 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.
get_source_detailReturn 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.