Repository navigation
docs(js): Drop manual wrapMcpServerWithSentry from MCP setup - #19881
Conversation
Co-Authored-By: Andrei Borza <[email protected]>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
1 Skipped Deployment
|
github-actions
Bot
added
the
Priority: Needs Triage
|
Please update the IS YOUR CHANGE URGENT? section of the PR description:
This information helps the Docs team prioritize your review. |
|
The change updates setup copy on the affected pages. Readers now see automatic instrumentation as the default. The plan checks client errors, HTTP 5xx, and pageload time on those pages. An issue escalates when errors or 5xx rise, or when pageload time rises. Monitoring in Services: Mention PlanWhat changedThe MCP setup pages now show a plain McpServer constructor as the default. Cloudflare pages still tell readers to wrap the server by hand. sentry-docs must deploy before this copy is live. RiskWrong copy can tell readers to skip the wrap on Cloudflare or on older SDKs. A broken MDX include can fail render for JavaScript MCP setup pages. The blast radius is those setup pages and the getting-started page. Intended effectThis copy change has no queryable effect in Sentry. Page loads do not prove the new sentences rendered. Absent looks like any successful page load. Telemetry cannot show the new copy. The executor cannot fill this axis from Sentry. Regression watchPageload counts are sampled spans at 30 percent. Do not treat them as full traffic. The 24 hour mcp-monitoring sample has 13 spans. That p95 value may move with traffic. The 7 day error window includes 29 events titled Event
Transaction name is Not observableThe new setup sentences are not in telemetry. No signal shows whether Cloudflare still shows the manual wrap. |
|
Verified in
|
This branch was successfully deployed
2 participants
Starting with SDK 11.1.0, the new default
mcpServerIntegrationinstruments everyMcpServer(@modelcontextprotocol/server2.x and@modelcontextprotocol/sdk>=1.9.0) automatically, so the setup docs no longer need to tell people to wrap their server by hand (getsentry/sentry-javascript#24529).The MCP Monitoring setup now shows a plain
new McpServer(...). The manual wrap is kept as the fallback for SDKs older than 11.1.0 or apps without automatic instrumentation, and it is still documented as the way to setrecordInputs/recordOutputsfor a single server, since a later wrap overrides the auto-wrap's defaults.Cloudflare doesn't get the integration, so it now has its own setup include that still wraps the server. The Hono include covers both cases. Bun and Next.js get a short note: on Bun this only works when you build with the Sentry Bun plugin, and on Next.js only in the Node.js runtime, not Edge. I also updated the product getting-started page and the data-collected page to match.
via Andrei Borza.
--
View Junior Session [Sentry]