Agents and MCP

Let your coding agent read and fix your production errors

Errilo has a remote MCP server. Your agent (Claude Code, Cursor, VS Code or an agent in CI) reads the issue, gets a stack trace that points to the right file at the right commit, fixes the code and marks the issue resolved. Included in every plan, the free one too. Errilo runs no AI model.

Updated

Errilo is in development. The MCP server runs at app.errilo.com/mcp; each connection method below says whether we have tested it.

What your agent gets

Tools

Eight tools, six to read and two to write:

Tools of the Errilo MCP server
ToolScopeWhat it does
list_projectsissues:readLists the projects the agent can see.
search_issuesissues:readSearches issues with filters: project, status, environment, release, text in the title.
get_issueissues:readReads an issue: status, occurrences, releases, stack trace and latest event.
get_eventissues:readReads another occurrence of the issue.
get_tag_distributionissues:readShows which browsers, versions, environments or URLs the issue hits.
get_releaseissues:readShows what a release contains: its commit, new issues and regressions.
update_issueissues:writeResolves an issue, resolves it in the next release, ignores it, assigns or unassigns it.
add_commentissues:writeComments on an issue, for example with the diagnosis and the link to the pull request.

And a fix_issue prompt that gives the agent a method: read the issue, check out the release commit, reproduce the error with a failing test, fix it, open a pull request (never a push to the main branch), comment, then mark the issue “resolved in the next release”. If the error comes back after the deploy, the issue regresses and you get an alert again.

No tool deletes anything. Search works with filters, not natural language: your agent turns your request into filters itself.

Connect from your editor

Add the server URL to your client. The first time, it opens Errilo in your browser: you sign in, choose the organization and the scopes, issues:read to read (the default) and issues:write to resolve, assign and comment. There is no token to copy.

Claude Code, in a terminal
claude mcp add --transport http errilo https://app.errilo.com/mcp

Then type /mcp in Claude Code to sign in.

In Cursor or VS Code, one click adds the server, then you sign in when the editor asks:

Add to Cursor Install in VS Code

Or add it to the configuration file by hand:

Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "errilo": { "url": "https://app.errilo.com/mcp" }
  }
}
VS Code: .vscode/mcp.json
{
  "servers": {
    "errilo": { "type": "http", "url": "https://app.errilo.com/mcp" }
  }
}

In VS Code, the MCP: Add Server command does the same. On claude.ai, open Settings, Connectors, add a custom connector and enter https://app.errilo.com/mcp.

Tested on 18 November 2026, from sign-in to resolving an issue: Claude Code with the /mcp sign-in, the claude.ai custom connector and MCP Inspector. Cursor and VS Code use the same MCP standard; their setups follow each client’s documentation, we haven’t tested them ourselves.

To cut an agent off, open Settings, Connected applications in Errilo and revoke its access: it stops working at once.

An agent in CI: a project token

An agent without a browser uses an access token restricted to one project. In Errilo, open Settings, API tokens, New token, tick issues:read (and issues:write to resolve and comment), and choose the project. The MCP server refuses tokens that aren’t restricted to a project.

CI
# ERRILO_TOKEN comes from your CI secrets
claude mcp add --transport http errilo https://app.errilo.com/mcp \
  --header "Authorization: Bearer $ERRILO_TOKEN"

The token (errilo_…) is shown only once. Keep it in your CI secrets or an environment variable, never in a committed file.

Tested on 18 November 2026 with Claude Code: reading, resolving and the fix_issue prompt.

To start the agent when an error appears, an Errilo alert can trigger a GitHub workflow. The GitHub alert channel sends a repository_dispatch event of type errilo-alert, once per issue, with the issue ID:

.github/workflows/errilo.yml
on:
  repository_dispatch:
    types: [errilo-alert]
jobs:
  fix:
    runs-on: ubuntu-latest
    steps:
      - env:
          ISSUE_ID: ${{ github.event.client_payload.issue_id }}
        run: echo "Errilo issue $ISSUE_ID"

The event also carries text from your errors, such as the title. Treat it as data: pass it through an environment variable, as above, and never write it straight into a shell command or an agent’s instructions.

A complete workflow, from the alert to the pull request, with its safeguards: auto-fix with Claude Code and GitHub Actions, step by step.

What keeps it safe

Included in every plan

The MCP server is included in every plan, the free one too. Errilo runs no AI model: the agent you already pay for (Claude Code, Cursor…) does the work, and your error data goes to it, nowhere else. There is nothing for us to bill.

Comparing with Sentry’s AI agent? Read Errilo as a Sentry Seer alternative. Still on Sentry? The migration guide takes one line.

Early access

We’re opening a private beta in summer 2027 for a handful of teams running Node.js or TypeScript in production. Join the waitlist and we’ll write when it opens.