[2026-07-28] Transport & observability headers/metadata
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- php
- Domain
- api, backend, observability
Research direction
Start with sub-issues #353, #354, and #355, then read their linked merged SEPs and spec PRs. For #353, check the per-request protocol version from #340 before implementing headers; for #354 and #355, follow the listed result metadata and trace-context requirements. Done means the applicable server and client changes for all three transport and observability features are implemented independently.
Written by the indexing model from the issue text.
Description
Tracking issue for the MCP Spec 2026-07-28 release — Transport & observability milestone.
Additive, non-breaking changes that surface routing/observability hints at the transport layer.
SEPs covered
| SEP | Title | Spec PR |
|---|---|---|
| SEP-2243 | HTTP Standardization (Mcp-Method / Mcp-Name headers) |
#2243 |
| SEP-2549 | TTL for List Results (ttlMs / cacheScope) |
#2549 |
| SEP-414 | OpenTelemetry Trace Context Propagation | #414 |
Sub-issues
- #353 — SEP-2243: Emit
Mcp-MethodandMcp-NameHTTP headers (server + client) - #354 — SEP-2549:
ttlMsandcacheScopeon list/read results - #355 — SEP-414: W3C Trace Context propagation via
_meta(server + client)
Notes
- All three SEPs are merged.
- All three are additive — implementable independently of the Milestone A stateless overhaul, though SEP-2243 should be gated on the per-request protocol version introduced in SEP-2575 (#340).
- Dominant language
- PHP
- Stars
- 1.6k
- Forks
- 173
- Avg merge
- 2d 49m
- Merged PRs (30d)
- 23
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from modelcontextprotocol/php-sdk
-
[Server] Handler type uses bare Closure, hard to decorate RegistryInterface under strict PHPStan OpenServer
Difficulty 1/5 Under an hour Newbie friendliness 78/100
modelcontextprotocol/php-sdk#468 · 2 comments ·
-
needs confirmation needs maintainer action Server
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/php-sdk#398 · 1 reaction ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
modelcontextprotocol/php-sdk#370 ·
-
enhancement
Difficulty 4/5 3-5 days Newbie friendliness 55/100
modelcontextprotocol/php-sdk#510 · 1 comment ·
-
bug
Difficulty 4/5 3-5 days Newbie friendliness 45/100
modelcontextprotocol/php-sdk#504 ·
All issues in modelcontextprotocol/php-sdk
Similar issues
-
priority: p3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
googleapis/librarian#7636 ·
-
0. Needs triage bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
nextcloud/fulltextsearch#1011 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
phpstan/phpstan-doctrine#794 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
Automattic/static-site-importer#1767 ·