MCP semantic conventions#2083
Conversation
brunobat
left a comment
There was a problem hiding this comment.
Thanks!
In general this seems reasonable.
Just added 2 comments.
Co-authored-by: Aaron Abbott <aaronabbott@google.com>
Co-authored-by: Aaron Abbott <aaronabbott@google.com>
Co-authored-by: Aaron Abbott <aaronabbott@google.com>
|
Draft of the blogpost in case it helps with the review: https://github.com/lmolkova/opentelemetry.io/blob/6fed6dfb4839b661ed269b67dc16f653f48ae9f4/content/en/blog/2026/mcp-semantic-conventions.md |
jsuereth
left a comment
There was a problem hiding this comment.
Nice! I like how you've worded the context propagation component to be forward compatible.
…en-telemetry/semantic-conventions#2083 - Change mcp.tool.name to gen_ai.tool.name - Change mcp.prompt.name to gen_ai.prompt.name - Change mcp.request.id to jsonrpc.request.id - Change rpc.jsonrpc.error_code to rpc.response.status_code - Update network.transport values from 'stdio' to 'pipe' and 'sse'/'http' to 'tcp' - Add gen_ai.operation.name attribute (value: 'execute_tool' for tools/call) - Update histogram bucket boundaries to match semantic conventions spec - Update tests to verify new attribute names Co-authored-by: stephentoub <2642209+stephentoub@users.noreply.github.com>
Updates FastMCP's telemetry to align with the new MCP semantic conventions from open-telemetry/semantic-conventions#2083. This gives us interoperability with other MCP implementations while keeping fastmcp.* attributes for things unique to our framework. Changes: - Span names now follow `{method} {target}` format (e.g., `tools/call greet`) - Added `mcp.method.name` and `mcp.resource.uri` attributes - Renamed `fastmcp.session.id` to standard `mcp.session.id` - Kept fastmcp.* attributes for server name, component info, provider details 🤖 Generated with Claude Code Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
|
Hey! We built a TypeScript implementation of these MCP semantic conventions in toad-eye — an open-source observability toolkit for MCP servers. What we implemented based on this spec:
Also added MCP-specific metrics ( 11 Grafana dashboards auto-provisioned, including 3 MCP-specific ones. Happy to share feedback on the spec from an implementer's perspective if that's useful. |
Fixes #2043
Adds the first version of MCP conventions including spans and basic metrics.
Implementations/prototypes:
Here's a draft of the blog: https://github.com/lmolkova/opentelemetry.io/blob/6fed6dfb4839b661ed269b67dc16f653f48ae9f4/content/en/blog/2026/mcp-semantic-conventions.md