Repository navigation
MCPIntegration reports stateless StreamableHTTP servers as mcp.transport "stdio" #7225
Description
How do you use Sentry?
Sentry Saas (sentry.io)
Version
2.64.0
Steps to Reproduce
-
Serve an MCP server over StreamableHTTP with StreamableHTTPSessionManager(app=server, json_response=True, stateless=True), mounted in a Starlette app.
-
Initialise the SDK with MCPIntegration().
-
POST a tools/call request to the mount path and let the tool return normally.
-
Inspect the resulting mcp.server span's attributes.
Versions: sentry-sdk==2.64.0, mcp==1.28.1, starlette==0.42.0, Python 3.13. The same result holds on mcp 2.x.
Expected Result
mcp.transport: "http". The server is reachable only over HTTP, so the transport should say so.
Actual Result
mcp.transport: "stdio" and network.transport: "pipe", with no mcp.session.id.
on our hosted MCP server, 100% of spans claim to be local stdio processes, and any query splitting local from hosted traffic on this attribute is silently meaningless.
Activity
linear-code commentedon Aug 20, 2026
PY-2738
alexander-alderman-webb commentedon Aug 20, 2026
Thanks @Snaylaker. We'll find a more principled way to determine the transport type.
Snaylaker commentedon Aug 20, 2026
I left #7224 up as a stopgap in case it's useful, but happy to close it if you'd rather take an other direction.
fix(mcp): don't report stateless StreamableHTTP servers as stdio (get…
fix(mcp): don't report stateless StreamableHTTP servers as stdio (#7224)