MCP server

Queringo exposes a Model Context Protocol (MCP) server so MCP-compatible AI tools and agents can query your workspace data through a standard interface. It is available on the Scale plan and above.

Connect

• Endpoint: /v1/mcp (Streamable HTTP transport).
• Auth: the same qg_live_ API key you mint in API keys. No separate MCP credential. The key's workspace, role, and scopes decide what the tools can see and do.
• Protocol: Streamable HTTP, protocol version 2025-03-26. The server advertises serverInfo.name = "queringo-mcp" and serverInfo.version in the initialize response so clients can display the connected version.

Every request must include these headers:

Configure your MCP client

Both snippets use the bearer-token transport. Paste your qg_live_... key in place of the placeholder; both files live in your home directory.

Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows):

{
  "mcpServers": {
    "queringo": {
      "transport": "streamable-http",
      "url": "https://app.queringo.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer qg_live_..."
      }
    }
  }
}

Cursor (~/.cursor/mcp.json):

{
  "mcpServers": {
    "queringo": {
      "url": "https://app.queringo.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer qg_live_..."
      }
    }
  }
}

Restart the client after saving the file. The server name (queringo) is what shows up in the client's tool picker; rename it freely.

Initialize and list tools

Two JSON-RPC calls verify a connection end-to-end:

curl https://app.queringo.com/v1/mcp \
  -H "Authorization: Bearer qg_live_..." \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2025-03-26" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "initialize",
    "params": {
      "protocolVersion": "2025-03-26",
      "clientInfo": {"name": "my-client", "version": "1.0"},
      "capabilities": {}
    }
  }'

initialize returns result.serverInfo.name = "queringo-mcp" and result.serverInfo.version (currently 1.0.0). Once initialized, list the tools:

curl https://app.queringo.com/v1/mcp \
  -H "Authorization: Bearer qg_live_..." \
  -H "Accept: application/json, text/event-stream" \
  -H "Content-Type: application/json" \
  -H "MCP-Protocol-Version: 2025-03-26" \
  -d '{"jsonrpc": "2.0", "id": 2, "method": "tools/list", "params": {}}'

Tools

The required scope column maps to the scopes selected when minting the key. A key with both scopes (or no scopes set, the default) can call every tool. A read-only key can call every tool except queringo_ask_data; an ask-only key can only call queringo_ask_data. tools/list and initialize work on any key regardless of scope so MCP clients can always discover the surface.

Call a tool with tools/call:

{
  "jsonrpc": "2.0",
  "id": 3,
  "method": "tools/call",
  "params": {
    "name": "queringo_ask_data",
    "arguments": {"question": "MRR last 30 days by plan"}
  }
}

Errors

Every error response is a JSON body with error_code + message (plus any context the gate adds), mirroring the REST /v1/* error shape so SDKs can use a single parser.

Plan-aware rate caps: Starter 60 rpm, Growth 600 rpm, Scale 6,000 rpm, Enterprise 60,000 rpm.

What's next

Combine the MCP server with Webhooks to push events into the same agent loop, or browse all docs at the documentation home.