Errorwatch

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 3, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

Errorwatch's local MCP server; no sign-in required; STDIO.

No AI overview yet: these facts come from the registry entry and the server itself.

Installation

In SourceWeft

  1. Open Errorwatch in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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

bash
npx @reneturcios/errorwatch list-organizations

Or run the container image:

bash
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

bash
export SENTRY_AUTH_TOKEN="your auth token"
errorwatch whoamierrorwatch list-organizationserrorwatch list-projects --org acmeerrorwatch list-releases --org acme --project weberrorwatch 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:

bash
npx -y @reneturcios/errorwatch mcp

MCP client configuration:

json
{  "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

bash
npm installnpm 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.

Source: README.md at commit 6f49b28

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestNov 3, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts