Skip to main content
Ultra records a trace record for every MCP operation. Traces capture the full lifecycle of a request — what was called, what arguments were sent, what came back, and how long it took.

​
Trace Record Structure

Field and metadata key names below are Ultra’s stable wire schema and don’t change with product terminology. See Terminology for how they map to Devices, Connectors, and Agents.
Each trace record contains:

​
Multi-Tenant Fields

When connected to Ultra Hub, traces also include:

​
Operation Types

​
Trace Metadata

The metadata map carries context that does not have a dedicated column. Keys are only present when Ultra has a value for them, so treat every key below as optional rather than guaranteed.

​
User

Populated when the device is linked to Ultra Hub and an identity was resolved for the request.

​
Client

Describes the MCP agent that made the request, taken from the agent’s clientInfo.
client.type is the normalized value (for example claude_desktop, cursor, vscode), while client.id preserves whatever the agent reported. Traces recorded before the normalization was introduced carry only client.id, so queries that need to cover historical data should fall back to it.

​
Server

Describes the upstream connector that handled the request. Which keys appear depends on the transport. server.transport reflects how the connector is configured, not the protocol that was negotiated at connection time.

​
Querying Traces

Traces are stored locally and can be queried through the dashboard.

​
Dashboard

The dashboard at http://localhost:8080 provides:
  • A list of all traces, sorted by timestamp
  • Filtering by operation type, upstream connector, status, and time range
  • Full request/response payload inspection for each trace
  • Duration and status breakdown
  • A Copy link button on each trace to share a deep link to it, and an Export control to download the filtered trace list as CSV or JSON (see Exporting table data and Sharing links)

​
Aggregate Statistics

Aggregate statistics are computed over your traces:
  • Total requests — Count of all operations
  • Success/error counts — How many succeeded vs failed
  • Average duration — Mean operation time
  • Requests by type — Breakdown by operation type
  • Requests by connector — Breakdown by upstream connector

​
OpenTelemetry Compatibility

Trace IDs and span IDs follow the W3C Trace Context specification, making Ultra traces compatible with any OpenTelemetry-compatible backend. See OTLP Export for configuration.