fix(mcp): standardize server naming and improve OAuth docs#17642
Merged
rahulchhabria merged 6 commits intomasterfrom May 6, 2026
Merged
fix(mcp): standardize server naming and improve OAuth docs#17642rahulchhabria merged 6 commits intomasterfrom
rahulchhabria merged 6 commits intomasterfrom
Conversation
- Standardize MCP server key to "Sentry" (capital S) in Amp and OpenCode config examples to match all other client configs - Update OpenCode CLI commands to match the config key - Add alert in main Setup section clarifying that Cloud transport requires OAuth + Streamable HTTP client support, with fallback options (mcp-remote bridge or stdio transport) - Improve OAuth troubleshooting with actionable guidance: link to mcp-remote workaround and stdio alternative, add URL check
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
sergical
reviewed
May 6, 2026
|
|
||
| When you first connect, you'll be prompted to log in with your Sentry organization and grant access. During authentication, you select which tool groups to expose — this keeps the context window focused on the tools you actually need. | ||
|
|
||
| <Alert> |
Member
There was a problem hiding this comment.
idk if this deems an alert. this is a pretty common thing for MCP servers to make sure it supports oauth and streamable http 🤔
| ```json | ||
| "amp.mcpServers": { | ||
| "sentry": { | ||
| "Sentry": { |
Member
There was a problem hiding this comment.
i would actually prefer we lowercase everything, i haven't seen any other mcp servers capitalize their mcp server names in configs
Lowercase all "sentry" keys in MCP client config blocks to match ecosystem convention — capitalized server names are uncommon across other MCP server docs. Demote the OAuth + Streamable HTTP requirement from an Alert to inline prose. This is a baseline expectation for cloud MCP servers, not a warning that warrants a callout. Co-Authored-By: Claude <noreply@anthropic.com>
…teps Follow-up to the JSON config key lowercasing. The opencode CLI commands and the Claude Code, Factory Droid, and v0 UI selection prompts also reference the configured server name — keeping those capitalized while the config keys are lowercase would mismatch what users see. Co-Authored-By: Claude <noreply@anthropic.com>
The v0.app MCP flow moved — the registry is now under Account Settings → Integrations → MCP Connections, and users search the catalog for the Sentry brand entry rather than picking a configured key. Co-Authored-By: Claude <noreply@anthropic.com>
sergical
approved these changes
May 6, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Addresses user feedback about inconsistencies and gaps in the MCP docs page (
docs/ai/mcp.mdx).Changes
Standardize MCP server key naming:
"sentry"→"Sentry"in Amp (VS Code) and OpenCode JSON config examples to match every other client config on the pageopencode mcp auth,opencode mcp logout) to match the updated config keyImprove OAuth documentation clarity:
<Alert>in the main Setup section explicitly stating that Cloud transport requires OAuth + Streamable HTTP support, with links to themcp-remotebridge and Stdio Transport as fallbacksmcp-remoteworkaround for clients without native OAuth/Streamable HTTPWhy
Users who don't get an OAuth prompt after following the main setup have no clear path to a fix — the
mcp-remoteworkaround was only mentioned in the collapsed "Other Clients" section, not in the setup flow or troubleshooting. The naming inconsistency (Sentryvssentry) across configs is a paper cut that erodes trust in the docs.Action taken on behalf of Rahul Chhabria.