TraceHawk // browser, PHP, Python, and Go errors Group · Count · File the ticket Ingest operational

MCP

The issues, logs, and telemetry, from the agent you already use.

Each person creates a key. It can search issues, error events, logs, and client telemetry by text, open one record, and change status, assignee, or priority for every project in the organization.

01 list_projects

Projects in this organization. Pass a slug or a name to the other tools, or * for every project.

02 list_members

People in this organization. Role is owner, admin, or member. Access is Admin or Developer. assign_issue accepts a name or an email from this list.

03 list_issues

Grouped issues on the key's project. search matches the title, short id, culprit, or exception type. Filter by status, project, or kind n_plus_one.

04 list_events

Events on one issue, newest first. Copy an event_id into get_issue to open an older event.

05 get_issue

One issue and one event: exception, stack, repeated query, request URL, and breadcrumbs.

06 search_events

Find an error by text in the exception, message, URL, transaction, stack, or breadcrumbs. The reply has short_id and event_id for get_issue.

07 list_logs

Log lines, newest first. search matches the message and the context. Session, user, and email are exact.

08 get_log

One log line, including its context.

09 list_telemetry

Client events and crashes. Every search word must match. type is event or crash.

10 get_telemetry

One telemetry record: message, error, and payload.

11 update_issue_status

Mark an issue unresolved, resolved, or ignored.

12 assign_issue

Assign a member by name or email. An empty assignee clears it.

13 set_issue_priority

Set low, medium, or high. Omit the priority, or pass an empty string, to clear it.

Client config Header or URL
Header

Paste this into the client's MCP config. Cursor reads it from mcp.json. The key stays in the Authorization header.

{
  "mcpServers": {
    "tracehawk": {
      "url": "https://tracehawk.net/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}
URL only

Some clients accept a URL and cannot send a header. Put the key in the path. Use the header form when the client can send headers, so the key stays out of the URL.

https://tracehawk.net/mcp/YOUR_KEY

Find a problem

list_issues searches the grouped issue: title, short id, culprit, and exception type. The title is the exception type plus the first 240 characters of the message.

search_events searches the event itself: exception text, message, URL, transaction, stack, and breadcrumbs. It does not read the request body. The reply has short_id and event_id. Pass those to get_issue.

list_logs searches log lines. The text matches the message and the context. get_log opens one line, including context. Session, user, and email are exact, not a substring.

list_telemetry searches client events and crashes. Every word must match the message, the error, the event name, or the stored payload text. Put a phrase in quotes to keep it as one word. get_telemetry opens one record.

Omit project to stay on the project the key was created on. Pass * for the organization. period defaults to the last 7 days: hour, 3h, day, 3d, week, 14d, or 31d. Logs are kept 14 days, so 31d returns the same log lines as 14d. Issues and telemetry are kept 31 days.

Create a key

Sign in, open MCP, and name the key after the machine or the person, such as Laptop. The token is shown once, as Authorization: Bearer …. Reloading the page hides it. The same page prints a config block named after the project slug, with the new token filled in. Creating a project does not create an MCP key.

The project key inside the snippet and inside TRACEHAWK_DSN cannot call these tools. Create the MCP key on the MCP page. You can keep 20 of your keys on one project. The name is required, at most 80 characters, and unique for you on that project.

A key created on one project works on every project in the organization. list_issues defaults to the project the key was created on. An owner or admin sees every key, including who created it. A member sees only the keys they created, and can delete those. An owner or admin can delete any of them.

Arguments

list_projects

No arguments. Returns the projects in the organization. Use a slug or a name as the project argument on list_issues.

list_members

No arguments. Returns each person with a name, an email, a role of owner, admin, or member, and access of Admin or Developer. An owner or admin has access Admin. A member has access Developer. assign_issue accepts a name or an email from this list.

list_issues

status is unresolved, resolved, ignored, or all. It defaults to unresolved. search matches the title, short id, culprit, or exception type. It does not look inside the stack. project is a slug or a name. Omit it for the key's own project. * covers the organization. kind accepts n_plus_one, which keeps N+1 Queries and N+1 API Calls and orders them heaviest first. sort is recent (last seen) or heaviest (event count, then users). It defaults to heaviest when the kind is n_plus_one, and to recent otherwise. limit defaults to 25 and is clamped to 1-50.

list_events

short_id is required, such as SHOP-14. Events come back newest first. limit defaults to 20 and is clamped to 1-50. Pass an event_id from this list to get_issue.

get_issue

short_id is required. event_id is optional and defaults to the latest event. The event includes the exception, up to 40 stack frames, breadcrumbs, tags, the request URL and method, and the trace spans. The reply also includes older_event_id and newer_event_id so the agent can step through the history. The request body is left out.

search_events

search is required, at least 2 characters, and at most 120. It matches the exception text, message, URL, transaction, stack, and breadcrumbs. A percent sign is literal. environment is an exact name. period, project, and limit work as they do on list_logs. The default period is week and the default limit is 25.

list_logs

search is optional. When set, it is a substring of the message or the context, at least 2 characters. session, user, email, environment, and area are exact. level is debug, info, notice, warning, error, critical, alert, or emergency. period defaults to week. limit defaults to 25 and is clamped to 1-50. Omit project for the key's project, or pass *.

get_log

log_id is required. It is the id from list_logs. The reply includes the message and the context. Context longer than 4,000 characters is cut, and context_truncated is true. A log from another project in the same organization can be opened by id.

list_telemetry

search is optional. Words are combined with AND. Text in quotes is one phrase. The match covers the message, the error, the event name, and the stored text of the payload. session, user, email, environment, and service are exact. level is debug, info, warning, or error. type is event or crash. period, project, and limit match list_logs.

get_telemetry

record_id is required. It is the id from list_telemetry. The reply includes the message, the error, and the payload. A payload longer than 4,000 characters is cut, and payload_truncated is true.

update_issue_status

short_id and status are required. Status is unresolved, resolved, or ignored.

assign_issue

short_id is required. assignee is a name or email from list_members. An empty assignee clears it.

set_issue_priority

short_id is required. priority is low, medium, or high. Omit it, or pass an empty string, to clear the priority.

What the client sends

The server speaks MCP over HTTP POST and accepts protocol versions 2024-11-05, 2025-03-26, and 2025-06-18. A GET or DELETE to the key URL is refused. An unknown key is rejected. The workspace MCP page is where a key is replaced: delete it, create another, and paste the new token. The old token stops working as soon as it is deleted.

Troubleshooting

Questions

Can I reuse the project key from the snippet?

No. The snippet key and TRACEHAWK_DSN receive events. An MCP key is created separately, by each person, on the MCP page.

Does one key cover every project?

Yes, inside that organization. list_issues, search_events, list_logs, and list_telemetry still default to the project the key was created on. Pass project * to read the rest. get_issue, get_log, and get_telemetry open a record from any project in the organization by id.

Which tool finds a phrase from a stack or a log line?

search_events for an exception, stack, breadcrumb, or URL. list_logs for a log message or its context. list_telemetry for a client event or crash. list_issues only matches the grouped title, short id, culprit, and exception type.

Who can see the keys?

An owner or admin sees every key and who created it. A member sees only the keys they created. The token itself is shown once.

Which config should I paste?

Use the Authorization header when the client can send headers. Use the URL with the key in the path when the client only accepts a URL.

Related

Ready to turn error noise into actionable issues?