@upgoose/mcp

MCP server for Upgoose — lets your AI coding agent read the errors your users are actually hitting, with full stack traces, breadcrumbs, release info and Upgoose's AI diagnosis, then resolve them once it ships a fix.

Setup

Create a token at upgoose.app/settings → API tokens, then point your agent at the server.

Claude Code

claude mcp add upgoose --env UPGOOSE_TOKEN=ugt_... -- npx -y @upgoose/mcp

Anything that reads an MCP config file (Cursor .cursor/mcp.json, VS Code .vscode/mcp.json, Windsurf ~/.codeium/windsurf/mcp_config.json, Claude Code .mcp.json):

{
  "mcpServers": {
    "upgoose": {
      "command": "npx",
      "args": ["-y", "@upgoose/mcp"],
      "env": { "UPGOOSE_TOKEN": "ugt_..." }
    }
  }
}

Tools

| Tool | What it does | | --- | --- | | list_projects | Projects in the account, with ids and whether error tracking is on | | list_error_groups | Production errors, newest activity first; unresolved by default | | get_error_group | One error in full — stack traces, breadcrumbs, tags, release, AI diagnosis and suggested fix | | set_error_group_status | Resolve or ignore up to 25 groups |

Environment

| Variable | Required | Default | | --- | --- | --- | | UPGOOSE_TOKEN | yes | — | | UPGOOSE_API_URL | no | https://api.upgoose.app |

The token

UPGOOSE_TOKEN is a secret. It grants read access to every error in the account and the ability to change error status, so treat it like any other API credential: keep it in the MCP config or your shell profile, not in committed source.

It is deliberately not the same thing as a project's DSN. The DSN (https://<key>@api.upgoose.app/<id>) is public — it ships inside your frontend bundle — and it can only write error events. A DSN key will not authenticate this server.

Revoking a token in Settings takes effect on the next request.

License

BSD-3-Clause