MCP for AI assistants

Bugtail speaks the Model Context Protocol, so an AI coding assistant can look at your errors itself instead of being shown screenshots of them. It reads the issue, the stack trace with source maps applied, the breadcrumbs and the logs around it, and with permission it can resolve, mute and comment.

There is nothing to install. The MCP server is part of your organisation's dashboard.

Connect

Create a token under Settings > API tokens. A Read only token can investigate; a Read and write token can also triage.
Right after you create it, the screen shows a configuration with the token filled in. Paste it into your MCP client.

It looks like this:

{
  "mcpServers": {
    "<organisation>": {
      "type": "http",
      "url": "https://<organisation>.bugtail.eu/mcp",
      "headers": { "Authorization": "Bearer <token>" }
    }
  }
}

The token is shown only once, so paste the configuration before you leave the screen. Any client that supports remote MCP servers over HTTP with a custom header works.

Tools

Tool	Needs	What it does
`list_projects`	read	Lists the projects in your organisation.
`search_issues`	read	Finds open issues, worst first, by text, level or project.
`get_issue`	read	Counts, status, releases, and occurrences per hour over the last day.
`get_latest_event`	read	The stack trace with source maps applied, the breadcrumbs and the browser.
`search_logs`	read	Log lines around the failure.
`resolve_issue`	write	Marks an issue as fixed. It becomes Regressed if it happens again.
`ignore_issue`	write	Mutes an issue, optionally for a number of hours.
`comment_on_issue`	write	Leaves a note on the issue for the rest of the team.

An assistant with a read-only token does not see the write tools at all. Issues can be named by their number or by their reference, such as SHOP-14.

Good to know

Changes are on record. Everything an assistant changes shows up in the issue's activity as done through MCP, and a comment is signed with the name of the person the token belongs to.
Counts outlive events. An issue keeps counting after its individual events have passed their retention period. An old issue can have a large count and no event left to show; the assistant is told so.