Back to Browse

Errorwatch MCP Server

Developer ToolsModerate5.7MCP RegistryLocal
Free

Server data from the Official MCP Registry

Organizations, projects, releases, and issues through the Sentry API.

About

Organizations, projects, releases, and issues through the Sentry API.

Security Report

5.7
Moderate5.7Moderate Risk

errorwatch is a focused Sentry API client that reads its token from SENTRY_AUTH_TOKEN, sends it only as a Bearer header to sentry.io, and exposes tools that match its stated purpose. No exfiltration, shell execution, hardcoded secrets, or dynamic code evaluation were found. The remaining findings are informational: the server can modify issues and post comments, and redirect handling is not explicitly restricted. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.

8 files analyzed · 8 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

SENTRY_AUTH_TOKENRequired

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-cloudcorprecords-errorwatch": {
      "env": {
        "SENTRY_AUTH_TOKEN": "your-sentry-auth-token-here"
      },
      "args": [
        "-y",
        "@reneturcios/errorwatch"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

errorwatch

errorwatch keeps an eye on a Sentry account from one small bin. An agent can confirm who a token belongs to, walk organizations, projects, and releases, search the issue stream with Sentry's own query syntax, open an issue and its latest event, change the issue's status, and read or leave comments on it. It runs from the command line or as an MCP server for agents.

A Sentry auth token is required. Put it in the SENTRY_AUTH_TOKEN environment variable; it is sent to the API as a Bearer token and never appears in output. When the variable is missing, every call fails with an error that names it.

This is a core subset of the Sentry API, not the whole surface: the hosted documentation search tools, the AI autofix (Seer) tools, profiling / traces / spans search, DSN and project creation and other admin operations, and organization statistics beyond issues are out of scope.

Install

npx @reneturcios/errorwatch list-organizations

Or run the container image:

docker run -i -e SENTRY_AUTH_TOKEN ghcr.io/cloudcorprecords/errorwatch

The container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.

CLI

export SENTRY_AUTH_TOKEN="your auth token"

errorwatch whoami
errorwatch list-organizations
errorwatch list-projects --org acme
errorwatch list-releases --org acme --project web
errorwatch search-issues --org acme --query "is:unresolved TypeError"
errorwatch get-issue --issue-id 123456

errorwatch --version

Exit codes: 0 on success, 1 when an API call fails (including a missing SENTRY_AUTH_TOKEN), 2 for usage errors.

MCP server

One bin serves both faces. The mcp subcommand starts a stdio MCP server:

npx -y @reneturcios/errorwatch mcp

MCP client configuration:

{
  "mcpServers": {
    "errorwatch": {
      "command": "npx",
      "args": ["-y", "@reneturcios/errorwatch", "mcp"],
      "env": { "SENTRY_AUTH_TOKEN": "your auth token" }
    }
  }
}

Tools

ToolInputWhat it returns
whoami(none)The authenticated user or token identity (GET /auth/).
list_organizations(none)Organizations the token can access.
list_projectsorganization_slug (required)Projects in the organization.
get_projectorganization_slug, project_slug (required)One project's details.
list_releasesorganization_slug, project_slug (required)Releases for the project.
search_issuesorganization_slug (required), project_slug, query, limit (optional)Issues matching the Sentry search query; uses the project issues endpoint when a project is given.
get_issueissue_id (required)One issue's details.
get_issue_eventissue_id (required), event_id (optional, defaults to latest)One event belonging to the issue.
update_issueissue_id (required), status, resolved_in_next_release, assigned_to, has_seen, is_bookmarked, is_subscribed (optional)The updated issue; only the fields given are sent.
list_issue_commentsissue_id (required)Comments (notes) on the issue.
create_issue_commentissue_id, text (required)The created comment.

Failed API calls are reported as tool errors carrying the HTTP status and, when Sentry provides one, its detail message.

Development

npm install
npm run build   # tsc -> dist/
npm test        # node test runner over test/*.test.ts, no network (fake fetch fixtures)
npm run dev     # run the CLI from source via tsx

License

MIT — see LICENSE.

Reviews

No reviews yet

Be the first to review this server!