Allows monitoring and interacting with a Sentry account, including checking token identity, listing organizations, projects, and releases, searching issues with Sentry query syntax, retrieving issue details and events, updating issue status and metadata, and listing or creating issue comments.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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.
npx @reneturcios/errorwatch list-organizationsOr run the container image:
docker run -i -e SENTRY_AUTH_TOKEN ghcr.io/cloudcorprecords/errorwatchThe container defaults to the MCP server (see below). Pass CLI arguments to use it as a CLI instead.
Related MCP server: @batontasks/mcp
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 --versionExit codes: 0 on success, 1 when an API call fails (including a
missing SENTRY_AUTH_TOKEN), 2 for usage errors.
One bin serves both faces. The mcp subcommand starts a stdio MCP
server:
npx -y @reneturcios/errorwatch mcpMCP client configuration:
{
"mcpServers": {
"errorwatch": {
"command": "npx",
"args": ["-y", "@reneturcios/errorwatch", "mcp"],
"env": { "SENTRY_AUTH_TOKEN": "your auth token" }
}
}
}Tool | Input | What it returns |
| (none) | The authenticated user or token identity ( |
| (none) | Organizations the token can access. |
|
| Projects in the organization. |
|
| One project's details. |
|
| Releases for the project. |
|
| Issues matching the Sentry search query; uses the project issues endpoint when a project is given. |
|
| One issue's details. |
|
| One event belonging to the issue. |
|
| The updated issue; only the fields given are sent. |
|
| Comments (notes) on the issue. |
|
| The created comment. |
Failed API calls are reported as tool errors carrying the HTTP status
and, when Sentry provides one, its detail message.
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 tsxMIT — see LICENSE.
This server cannot be deployed
Enable secure connectivity between Sentry issues and debugging data, and LLM clients, using a Model Context Protocol (MCP) server.
MCP server for Sentry - error monitoring, issue tracking, and debugging for AI assistants
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
Argentic MCP server: run and inspect long-running agents on Argentic.
