Quri

Claude / MCP clients

Last updated 2026-06-14

What this unlocks

Add Quri to Claude (or another MCP client) and you can use your Quri tools right inside a chat — ask it to query a metric, run an audit, or connect a source, and it answers from your own data instead of you switching over to the Quri app.

Connect it in Quri

  1. This guide runs the other way round from the rest: you are wiring Quri into Claude as a tool, not connecting a data source into Quri. Quri exposes a hosted MCP endpoint at https://api.myquri.com/mcp.
  2. Get your Quri API key first — open /app/settings in Quri and copy (or create) the API key for your account. The key is tenant-scoped, so the client only ever reaches your data.
  3. The hosted MCP endpoint is switched on by the Quri operator (it stays off until then). If https://api.myquri.com/mcp does not respond yet, ask us to enable it for your account.
  4. Add the endpoint to your client using the provider steps below, authenticating with Authorization: Bearer <your Quri API key>.
  5. Once connected, the tools you see match your plan — query_metrics, run_audit, connect_source, explain_feature and the rest of your visible tools — nothing your plan does not include.

Get your credentials

  1. claude.ai (Pro or Max): open Settings, go to Customize → Connectors, click the "+" and choose "Add custom connector". Paste https://api.myquri.com/mcp as the remote MCP server URL. Note that claude.ai reaches your server from Anthropic's cloud over HTTPS — the hosted Quri endpoint already meets that; a self-hosted Quri must be public over HTTPS too.
  2. claude.ai (Team or Enterprise): an owner adds it under Organization settings → Connectors → Add → Custom → Web with the same URL, then members click Connect on it under Customize → Connectors.
  3. Claude Desktop: open Settings → Developer → Edit Config, which opens claude_desktop_config.json (~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows). Add a server that runs the mcp-remote bridge with your bearer key, then save and restart Claude Desktop: {"mcpServers":{"quri":{"command":"npx","args":["-y","mcp-remote","https://api.myquri.com/mcp","--header","Authorization: Bearer YOUR_QURI_API_KEY"]}}}
  4. Other MCP clients (Cursor and the like): point the client at https://api.myquri.com/mcp as a remote/HTTP MCP server and send the Authorization: Bearer <key> header — the same endpoint and key work anywhere that speaks MCP over HTTP.
  5. ChatGPT: its connector flow accepts a remote MCP URL but does not support API-key headers today (OAuth only), so Quri's bearer-key endpoint cannot be added there yet. Use Claude or another header-capable client until that gap closes.

Access Quri reads with

  • Authentication is a per-tenant bearer API key (Authorization: Bearer <key>) — the client sends it on every call and only ever reaches your own tenant's data.
  • The tools exposed are exactly the ones your Quri plan grants; the endpoint never reveals a tool your plan does not include, so the client cannot do more in Quri than you can.

Troubleshooting

Claude says it cannot connect to the Quri server, or the endpoint does not respond.
The hosted MCP endpoint is off until the Quri operator enables it for your account. If https://api.myquri.com/mcp is not answering, ask us to switch it on. Also confirm the URL is exact and uses HTTPS — claude.ai will only reach a public HTTPS server.
I connected but every call comes back unauthorized (401).
The bearer API key is missing, mistyped, or revoked. Re-copy it from /app/settings in Quri and make sure the header is exactly "Authorization: Bearer <key>" — in Claude Desktop that is the --header value in claude_desktop_config.json; on claude.ai it is set through the connector's authentication step.
Quri connects but I do not see the tools I expected.
The endpoint only exposes the tools your plan grants, so a tool you do not have simply will not appear. Check your plan in Quri, and after editing claude_desktop_config.json restart Claude Desktop so it re-reads the server and re-lists the tools.
Can I add this to ChatGPT the same way?
Not yet. ChatGPT's connector flow authenticates with OAuth and does not accept an API-key header, while Quri's endpoint authenticates with a bearer key — so the key-based setup that works in Claude does not work in ChatGPT today. Use Claude Desktop, claude.ai, or another client that lets you send an Authorization header.

Related guides