What's new

We’ve released our MCP server. This means you can now connect Claude Code, Cursor, and other MCP-compatible AI agents to Trace0 to investigate errors, analyze performance, and troubleshoot issues faster.

Authentication

The Trace0 MCP server uses OAuth for authentication. Simply add the server URL (https://app.trace0hq.com/api/mcp) to your MCP client, and you’ll be redirected to your browser to sign in to your Trace0 account and authorize access. See our docs for full instructions.

Tools

The Trace0 MCP server provides the following tools for querying your environments, services, transactions, logs, and metrics:

Tool	Description
get_environments	Returns the names of all environments in the authenticated user’s Trace0 account.
get_services	Returns the name and programming language of all services in the given environment.
get_transactions	Returns the summaries of transactions matching the specified filters.
get_transaction_detail	Returns the transaction details for the given transaction ID.
get_log_count	Returns the number of logs matching the specified filters, aggregated by service name, severity level and time bucket.
get_service_metric_summaries	Returns metric summaries for all services in the given environment and time period.
get_service_metrics	Returns detailed metrics for a specific service in the given environment and time period, aggregated by time bucket.

Fair Use Limits

The Trace0 MCP server comes with the following fair-use limits:

• 50,000 monthly tool calls

Once a limit is exceeded, the MCP server will return an error describing the applicable restriction.

If you require higher limits, please contact us at hello@trace0hq.com to discuss.

We’ve shipped new transaction search functionality. You can now apply the following filters to your transaction search:

• Latency — set a minimum or maximum duration in milliseconds or seconds to focus on slow or fast requests.

• HTTP Status Code — filter to all 4xx errors, all 5xx errors, or a specific code like 404 or 503.

• Endpoint — filter by the endpoint that handled the request.

• Log Search — show only transactions where any of its log entries contain the search term.

How to use it

Open the Transactions screen and click the More Filters icon in the top right:

You can then add additional filters from the pop-up modal. Filters are combined using AND logic, so only transactions matching all applied filters are returned, including any already set in the Transactions screen, such as Service or Time Period.