Repository navigation
Conversation
Config Audit |
🎉 All green!🧪 All tests passed 🎯 Code Coverage (details) 🔗 Commit SHA: 9f4ce67 | Docs | View more details | Give us feedback! |
BenchmarksBenchmark execution time: 2026-11-10 02:59:40 Comparing candidate commit 9f4ce67 in PR branch Found 0 performance improvements and 0 performance regressions! Performance is the same for 415 metrics, 1 unstable metrics.
|
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
b3c972f to
88bc236
Compare
Codex Review Summary: ✅ CompletedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
…info # Conflicts: # contrib/mark3labs/mcp-go/tracing.go
What does this PR do?
Tags MCP server
initializeand tool call spans with the calling client's self-reported identity:mcp_client_name,mcp_client_title,mcp_client_version. Applies tomodelcontextprotocol/go-sdkandmark3labs/mcp-go._meta(io.modelcontextprotocol/clientInfo, sent on every 2026-07-28 request), then fall back to the session'sinitializehandshake._metaand the session through fields that exist in the pinned SDKs (go-sdk v1.4.1, mcp-go v0.42.0), so no version changes. Newer SDKs get the same tags.instrmcp.ClientInfoTags,instrmcp.ClientInfoTagsFromValue.client_nameandclient_versiontags oninitializespans are unchanged.Known limitations:
mcp_client_*tags.Implementationhas no title.Motivation
Previously only the
initializespan had client info, so tool calls could only be tied to a client by joining onmcp_session_id, which stateless servers do not have. This matches dd-trace-py #21189 and #21190.Tested on the pinned SDKs and locally on go-sdk v1.8.0 and mcp-go v1.5.0.
🤖 Generated with Claude Code