MCP server

Trefur exposes a read-only MCP server so MCP-aware clients (Claude Desktop, Cursor, Claude Code) can query trace data and run observability data without leaving their tool. Model Context Protocol is a launch-day surface for Trefur.

Read tools

The MCP server exposes a read-only surface for inspecting agents, runs, and traces. Mint a key with the mcp:read scope checkbox enabled.

• trefur.discover_agents — enumerate the agents the caller's tenant can see, with name, version, and owner.
• trefur.list_runs — recent runs for an agent, with status, start / end timestamps, and a per-run latency + cost summary.
• trefur.search_steps — search the steps across runs (tool calls, retries, LLM messages) to find a specific event.

MCP-native debugging

Because Trefur ships an MCP server, an MCP-aware client (Claude Desktop, Cursor, Claude Code) can ask Trefur about a recent run in-line — no context-switch to the dashboard. Useful for live debugging: paste a trace ID and ask the model to walk you through what the agent did.

Claude Desktop config

{
  "mcpServers": {
    "trefur": {
      "url": "https://mcp.trefur.com/mcp/v1",
      "headers": {
        "Authorization": "Bearer trf_obs_REPLACE_ME"
      }
    }
  }
}

Mint a key in your tenant settings with the mcp:read scope checkbox enabled.

Key prefix

The MCP handler accepts trf_obs_* keys minted with the mcp:read scope. Other key types are rejected with a named error code.