How do I query my agents’ traces from inside Cursor?

Rius lets you query your agents’ traces from Cursor by adding the Rius MCP server to your Cursor MCP config and signing in with your Rius account. Once connected, you ask questions in plain language and Cursor answers from your real telemetry: trace lists, cost and token summaries, alerts and full span waterfalls. The server URL is https://mcp.eu.console.rius-glassflow.com/mcp, and the server key is rius.

How it works

The Rius MCP server is an endpoint your AI client connects to for reading your telemetry. It uses streamable HTTP and OAuth 2.1. When you add it to Cursor and approve it, Cursor opens your browser for the Rius sign-in and handles the flow for you.

After you sign in, Cursor sees the workspaces your Rius user can access and picks the right tool for each question. Reading is open to every member of a workspace. Every tool carries a hint that says whether it only reads or changes something, so Cursor can auto-approve reads and ask you before a change. Nothing the server offers can create, rename or delete workspaces, or change members. Those stay in the console.

If you use the Rius plugin for Cursor (beta), it already registers this server as rius, so you do not add it again. Sign it in by clicking Connect next to rius in Cursor’s MCP settings, or by running cursor-agent mcp login rius. Sending traces and querying them are separate sign-ins: the plugin’s own sign-in sends traces, and the MCP sign-in lets you query them. Rius records each MCP call’s tool, outcome, latency and structural arguments for 30 days, and never stores tool results.

Set it up

1. Add the server to ~/.cursor/mcp.json for all projects, or to .cursor/mcp.json for one project:

{
  "mcpServers": {
    "rius": {
      "url": "https://mcp.eu.console.rius-glassflow.com/mcp"
    }
  }
}

2. Approve the server under Settings → MCP in Cursor. Complete the browser sign-in with your Rius account. Some clients show the server as connected before the sign-in finishes, so if Cursor lists no tools, check that you finished it.
3. Verify the connection by asking Cursor: “Who am I in Rius, and which workspaces can I access?” Cursor should call the get_me tool and answer with your email and a table of workspaces.
4. For a Cursor session that runs without a browser, use a read-scoped API key instead of OAuth. Mint it from the Connect an agent button on the console’s MCP page, or in Settings → API keys with the Query data (read) capability. The key is shown once, so store it as a secret. Ingest keys, the kind the SDK uses, cannot query. Then add a headers block:

{
  "mcpServers": {
    "rius": {
      "url": "https://mcp.eu.console.rius-glassflow.com/mcp",
      "headers": { "Authorization": "Bearer ri_..." }
    }
  }
}

If you also have the Rius plugin, which registers an OAuth server named rius, give this key-based entry its own name, such as rius-key. 5. If the sign-in loops or reports an auth error, remove the server and add it again. A stale cached token after a long idle period is the usual cause.

For every other client’s config, the full tool list and the headless details, see MCP.

What you get

You query your telemetry without leaving the editor. Cursor chooses the tools, and you ask things like:

• Traces: “List the failed runs from this week and show me what went wrong in the worst one.” Cursor lists traces filtered by status, then opens the span waterfall of one trace.
• Traffic and cost: “Summarize my agent traffic over the last 24 hours.” You get traces, LLM calls, error rate, cost, tokens and latency percentiles. “Which service is spending the most right now?” works the same way. Costs are list-price estimates in US dollars, not billed amounts.
• Agents and users: which agents exist, their error groups, how two versions of an agent compare, and what each end user’s activity looks like.
• Alerts: what is firing, the detail of one alert, and swallowed errors, the failures an agent hides from its caller.

An OAuth session acts with your role. Alert management, create_api_key and spend notices work only for admins, as in the console. An API key reaches the single workspace it was created in. It is read-only unless an admin minted it with alerts:manage or channels:manage in the Connect an agent dialog. No key can acknowledge an alert or mint other keys.

If you want Cursor sessions themselves to show up as traces, that is a separate setup. See Coding agents, where Cursor (beta) has no token counts or cost because its hooks do not report usage.

When something else fits

• Use the Rius console when you want to browse the trace list, the waterfall and map views, or share a frozen filtered view with a teammate.
• Use a read-scoped API key when the agent runs in CI or on a schedule with no browser to complete the OAuth flow.
• Use the same server URL in any other MCP client that supports remote servers, such as Claude Code or Codex.

Related