docs(cloudflare): Recommend span streaming for MCP

[betegon]

DESCRIBE YOUR PR

Cloudflare MCP work can finish after the Worker returns its HTTP response. In the static trace lifecycle, those late spans depend on a transaction snapshot that may already have been sent.

We verified this with two deployed Cloudflare Workers running byte-identical MCP 2026-07-28 bundles against the published JavaScript SDK. traceLifecycle: "static" lost the late child, while traceLifecycle: "stream" recorded it exactly once with the MCP operation as its parent.

This promotes MCP Monitoring to a top-level platform feature alongside Agent Tracing across supported JavaScript guides. Each framework page now shows the required wrapMcpServerWithSentry setup directly, including the runtime-specific imports for Hono. The Cloudflare page makes clear that wrapping the MCP server enables MCP instrumentation, while traceLifecycle: "stream" controls how the resulting spans are delivered. The Agent Tracing overview keeps its contextual MCP link, and the previous Tracing → Instrumentation → Instrument MCP Servers URL redirects to the new feature route.

The general Cloudflare waitUntil() limitation now recommends stream mode first. forceTransaction remains documented as the fallback for applications that need to keep the static lifecycle.

Related to getsentry/sentry-javascript#23427.

IS YOUR CHANGE URGENT?

• Urgent deadline (GA date, etc.)
• Other deadline
• None: Not urgent, can wait up to 1 week+

SLA

• Teamwork makes the dream work, so please add a reviewer to your PRs.
• Please give the docs team up to 1 week to review your PR unless you've added an urgent due date to it.

Thanks in advance for your help!

PRE-MERGE CHECKLIST

• Checked Vercel preview for correctness, including links
• PR was reviewed and approved by any necessary SMEs (subject matter experts)
• PR was reviewed and approved by a member of the Sentry docs team

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
develop-docs	Ready	Preview	Aug 14, 2026 5:20pm
sentry-docs	Ready	Preview	Aug 14, 2026 5:20pm

[sfanahata]

Is it common for us to have this type of recommendation listed in all JS frameworks? I would assume we'd have it in the browser one perhaps? Or maybe I'm misunderstanding what we're trying to say here.

If I'm on a selected SDK, and we support it, this is a confusing thing to be reading. I'm also assuming I can use these attributes even in supported SDKs?

@betegon , can you help clarify and I can make a suggestion for rewording?

[betegon]

hmm great question. i'm not sure if this is common, i'll look it up. there's a bunch of official (from anthropic) MCP SDKs. we support JS and Python for now, there's GO, PHP and some more.

>if I'm on a selected SDK, and we support it, this is a confusing thing to be reading. I'm also assuming I can use these attributes even in supported SDKs?

fair, you shouldn't use it if you're in a supported SDK, although maybe you want? say you just want to record a couple of span attributes yourself.

thanks for looking a this btw!

[sfanahata]

@betegon - can we clean up the language about "unsupported SDKs" before merging?

[betegon]

yes! looking at your comment to make those things as clear as possible