Which part? Which one?
MCP
Description
Description
The Sentry MCP server registers with different casing depending on the installation method, which causes confusion and broken setups:
- @sentry/mcp-server (npm package with access token) — registers as lowercase sentry, producing tool prefixes like mcp__sentry__whoami, mcp__sentry__find_organizations, etc.
- OAuth-based setup (via ~/.sentry/mcp.json) — registers as capitalized Sentry, producing tool prefixes like mcp__Sentry__whoami, mcp__Sentry__find_organizations, etc.
Impact
If a user tries both setup methods (or switches from one to the other), they end up with two Sentry MCP servers that appear to be the same thing but have different names and different auth states. In my case:
- mcp__sentry__* (lowercase) — returned 400/403 errors on every call
- mcp__Sentry__* (capitalized) — worked correctly
This is confusing to debug because the tools appear identical aside from casing, and AI coding assistants (Claude Code, Cursor, etc.) surface both sets of tools without making the distinction obvious.
Expected behavior
The server name should be consistent (sentry or Sentry) regardless of installation method. The docs at https://docs.sentry.io/ai/mcp/ should clarify what name each method uses, or ideally both methods should
register with the same name so they can't conflict.
Environment
- Claude Code CLI
- macOS
- @sentry/mcp-server@latest via npx
Suggested Solution
Standardize on lowercase sentry for the server name in both the npm package and OAuth-based setup methods. If different casing is intentional (e.g., to distinguish auth methods), document this explicitly on the MCP setup page and warn users that having both active will create duplicate tool registrations.
Which part? Which one?
MCP
Description
Description
The Sentry MCP server registers with different casing depending on the installation method, which causes confusion and broken setups:
Impact
If a user tries both setup methods (or switches from one to the other), they end up with two Sentry MCP servers that appear to be the same thing but have different names and different auth states. In my case:
This is confusing to debug because the tools appear identical aside from casing, and AI coding assistants (Claude Code, Cursor, etc.) surface both sets of tools without making the distinction obvious.
Expected behavior
The server name should be consistent (sentry or Sentry) regardless of installation method. The docs at https://docs.sentry.io/ai/mcp/ should clarify what name each method uses, or ideally both methods should
register with the same name so they can't conflict.
Environment
Suggested Solution
Standardize on lowercase sentry for the server name in both the npm package and OAuth-based setup methods. If different casing is intentional (e.g., to distinguish auth methods), document this explicitly on the MCP setup page and warn users that having both active will create duplicate tool registrations.