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:
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.
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:
[Server] Add request handler for resource templates #89
[Server] Add missing handler for resource subscribe/unsubscribe handlers #220
[Server] Add missing handler for resource subscribe/unsubscribe handlers #220
[Server] Add
completion/completehandler, centralize provider logic, and move completion capability #97And 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.