modelcontextprotocol / modelcontextprotocol/php-sdk

[2026-07-28] Governance: deprecations, lifecycle, conformance, SDK tier

Open
#339 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

2026-07-28 Client documentation enhancement improves spec compliance Server
Dominant language
PHP
Stars
1.6k
Forks
173
Avg merge
2d 49m
Merged PRs (30d)
23

Description

Tracking issue for the MCP Spec 2026-07-28 releaseGovernance & lifecycle milestone.

Coherent governance bundle: lifecycle policy (2596) governs what gets deprecated, conformance tests (2484) gate when SEPs go Final, and SDK tiers (1730) measure how well each SDK keeps up. SEP-2577 is the first concrete deprecation pass under the new policy.

SEPs covered

SEP Title Spec PR
SEP-2577 Deprecate Roots, Sampling, and Logging #2577
SEP-2596 Feature Lifecycle and Deprecation Policy #2596
SEP-2484 Conformance Tests required for Final status #2484
SEP-1730 SDK Tiers definition #1777

Sub-issues

  • #365 — SEP-2577: Mark Roots/Sampling/Logging @deprecated, emit notices, document migration
  • #366 — SEP-2596: Adopt MCP feature lifecycle policy; document PHP SDK BC promise
  • #367 — SEP-2484: Wire SEP traceability files into conformance test runner
  • #368 — SEP-1730: Target SDK Tier 2 classification — gap analysis, roadmap, dependency policy

Notes

  • All four SEPs are merged.
  • SEP-2577: implementations of Roots/Sampling/Logging stay — only public APIs gain @deprecated, plus runtime notices. Minimum 12-month removal window per SEP-2596.
  • SEP-1730: realistic target is Tier 2 immediately, Tier 1 post-1.0.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with sub-issues #365–#368 and their linked SEP material, especially the conformance test runner and PHP SDK BC promise mentioned in the issue. Done means completing the four governance tasks: deprecation notices and migration documentation, lifecycle adoption, SEP traceability in conformance tests, and the SDK Tier 2 gap analysis and roadmap.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
developer-experience, documentation, testing-qa
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.