ADFA-4305 Add Sentry MCP server config

[hal-eisen-adfa]

Registers the Sentry MCP server at project scope so contributors can query Sentry issues/events through Claude Code's MCP integration. Per-user OAuth is performed via /mcp authenticate; no shared secrets.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 9e35e0ca-a2ff-432f-ac4f-01e234617052

📥 Commits

Reviewing files that changed from the base of the PR and between 3c14345 and 830600f.

📒 Files selected for processing (1)

• .mcp.json

---

📝 Walkthrough

Sentry MCP Server Configuration

• Adds .mcp.json configuration file to register the Sentry MCP server at project scope
• Enables contributors to query Sentry issues and events through Claude Code's MCP integration
• Uses HTTP-based MCP server pointing to https://mcp.sentry.dev/mcp
• Authentication handled via per-user OAuth through the /mcp authenticate endpoint with no shared secrets

Risks & Best Practices

• External Service Dependency: Introduces a hard dependency on mcp.sentry.dev availability; service outages will impact the integration
• OAuth Configuration: Relies on proper OAuth configuration at the application level - ensure the /mcp authenticate endpoint is properly implemented and secured
• No Secret Management: While per-user OAuth avoids shared secrets (good practice), verify that OAuth token storage and refresh mechanisms are securely implemented
• Project-Wide Access: All project contributors will have access to this MCP server; ensure appropriate access controls are in place at the Sentry organization level if needed

Walkthrough

This PR adds a new .mcp.json configuration file that registers a Sentry HTTP server within the MCP servers registry, pointing to the Sentry MCP endpoint at https://mcp.sentry.dev/mcp.

Changes

MCP Server Configuration

Layer / File(s)	Summary
Sentry HTTP server endpoint .mcp.json	A new .mcp.json file defines mcpServers.sentry with type: "http" and url: "https://mcp.sentry.dev/mcp".

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

🐰 A config so neat, Sentry takes its seat,
HTTP endpoint now complete,
One little JSON to make protocols meet—
Integration looks sweet! ✨

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title directly describes the main change: adding Sentry MCP server configuration to the project, which aligns with the file summary showing a new .mcp.json file with Sentry MCP configuration.
Description check	✅ Passed	The description is clearly related to the changeset, explaining the purpose of the MCP configuration addition and how it enables querying Sentry through Claude Code's integration.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ADFA-4305-add-sentry-mcp

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}