| name | mcp-qa |
| description | QA MCP tool changes with local CLI and real agent clients. Use when explicitly invoked via /mcp-qa or when asked to QA MCP tool changes end-to-end. |
Verify MCP tool behavior end-to-end before committing or creating a PR. Prefer
agent-callable paths over browser or inspector workflows.
1. Quality Gate
pnpm run tsc && pnpm run lint && pnpm run test
Fix any failures before proceeding.
2. Stdio CLI
This is the primary QA path for tool behavior. Stdio runs the local MCP server
against prod Sentry without depending on the Cloudflare worker, local /mcp
route, or Cloudflare OAuth configuration.
When validating code or tool changes, build first because the test client
launches packages/mcp-server/dist/index.js:
pnpm -w run build
Check auth first:
pnpm --filter @sentry/mcp-server start auth status
If no cache exists, warm the device-code cache:
pnpm --filter @sentry/mcp-server start auth login
Device-code auth uses the bundled stdio public client ID, requires no client
secret, is separate from the Cloudflare OAuth app, and caches the token in
~/.sentry/mcp.json.
First prove startup and auth:
pnpm -w run cli --transport stdio --list-tools
pnpm -w run cli --transport stdio "who am I?"
Then prove the changed behavior with a realistic prod prompt. Choose a prompt
that requires the new or modified tool path, uses real org/project/resource
inputs, and asks for enough detail to prove the endpoint response is usable.
pnpm -w run cli --transport stdio \
"<prompt that exercises the changed MCP behavior against prod data>"
