GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
作者提供的说明(英文原文)
Organizations, projects, releases, and issues through the Sentry API.
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
打开 Claude Desktop → Settings → Developer → Edit Config,把下面的内容粘贴到 claude_desktop_config.json
{
"mcpServers": {
"errorwatch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/errorwatch",
"mcp"
]
}
}
}在终端中运行这条命令
claude mcp add errorwatch -- npx -y @reneturcios/errorwatch mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"errorwatch": {
"command": "npx",
"args": [
"-y",
"@reneturcios/errorwatch",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"errorwatch": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reneturcios/errorwatch",
"mcp"
]
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
这个服务器在你的电脑上运行,而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
它在你的电脑上运行;安装后,工具列表会显示在你的 AI 应用中。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过 GitHub 账户 CloudCorpRecords 验证,该账户拥有此仓库
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
它在你的电脑上运行,没有互联网端点
在你的电脑上运行,改用本地设置
它在你的电脑上运行;我们只能读取互联网端点的工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在你的电脑上运行。你的 AI 应用会在需要时启动它,数据不会经过作者的服务器(除非它自己调用在线服务)。
GitHub 仓库最后更新于–,最新版本(0.1.0)于4天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Node.js, Docker。
同一分类中有:GitHub, Desktop Commander, Cloudflare MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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-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.
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.
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" } } } }
| Tool | Input | What it returns |
|---|---|---|
whoami | (none) | The authenticated user or token identity (GET /auth/). |
list_organizations | (none) | Organizations the token can access. |
list_projects | organization_slug (required) | Projects in the organization. |
get_project | organization_slug, project_slug (required) | One project's details. |
list_releases | organization_slug, project_slug (required) | Releases for the project. |
search_issues | organization_slug (required), project_slug, query, limit (optional) | Issues matching the Sentry search query; uses the project issues endpoint when a project is given. |
get_issue | issue_id (required) | One issue's details. |
get_issue_event | issue_id (required), event_id (optional, defaults to latest) | One event belonging to the issue. |
update_issue | issue_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_comments | issue_id (required) | Comments (notes) on the issue. |
create_issue_comment | issue_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.
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
MIT — see LICENSE.