modelcontextprotocol / modelcontextprotocol/php-sdk
[Server] (Re-)Implement missing Notification & Request Handlers
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 1.6k
- Forks
- 173
- Avg merge
- 2d 49m
- Merged PRs (30d)
- 23
Description
For kicking off this SDK we used the Noticiation and Request handlers shipped with the Symfony MCP SDK and adopted schema component and registry.
But the MCP schema supports way more requests and notifications, that would need handlers as well. On php-mcp side this was the responsibility of the Dispatcher implementation.
Still open are:
- ListResourceTemplatesRequest
#89 - ResourceSubscribeRequest
#220 - ResourceUnsubscribeRequest
#220 - SetLogLevelRequest
- CompletionCompleteRequest
#97 - CancelledNotification
And potentially other requests and notification of the protocol.
Please announce yourself and create corresponding sub-issues before working on a specific handler - so we can avoid duplicate effort.
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.
Research direction
Start by reviewing the existing handlers under src/Server/NotificationHandler and src/Server/RequestHandler, then compare their coverage with the Symfony MCP SDK and php-mcp's Dispatcher.php. The issue identifies SetLogLevelRequest and CancelledNotification as still open, while other protocol gaps may remain. Done means agreed sub-issues and corresponding handlers for the missing protocol requests and notifications.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100