Support for MCP v2025‑03‑26 & full notifications/cancelled capability

[Jens-dev]

📝 Description

We’re trying to connect AnythingLLM (latest version using MCP v2025‑03‑26) with the Laravel MCP server, but encountering two major roadblocks:

1. Protocol version mismatch
   • Client initiates handshake with:

protocolVersion": "2025-03-26"

but the server only supports 2024-11-05.

Logs report: Client requested unsupported protocol version: 2025‑03‑26 {"supportedVersions":["2024‑11‑05"]}

•	Result:
•	Server rejects initialization.
•	AnythingLLM either loops back to older spec or fails altogether.

2. notifications/cancelled not implemented
   • Config has:

'capabilities' => [
  'notifications' => [
    'initialized' => true,
    'cancelled'   => true,
    'initializedOk' => true,
  ],
  …
]

and server is restarted accordingly.

Still, log shows: MCP Processor caught McpServerException {"method":"notifications/cancelled","code":-32601,"message":"Method not found: MCP capability 'notifications' is not enabled on this server."}

•	Reason:
•	AnythingLLM receives a ping timeout and dispatches notifications/cancelled.
•	Server rejects it, causing client disconnection.

⸻

✅ Steps already taken
1. Successful MCP handshake up to initialize + notifications/initialized + resources/list via cURL.
2. Upgraded package to latest version v2.1.0 with Streamable HTTP.
3. Fully configured config/mcp.php for notifications.
4. Cleared config/routes caches and restarted server.
5. Observed persistent logs for protocol and “notifications” errors.

⸻

🚀 Expected behavior
• Server supports 2025‑03‑26 protocol version (and optionally 2024‑11‑05 for legacy clients).
• Fully implements notifications/cancelled, along with other MCP notification methods.
• Allows AnythingLLM handshake to complete, keeping SSE connection alive and avoiding client drop.

⸻

Happy to provide more logs, config files, or curl traces if needed. Thanks for your support! 😊

Log:

[2025-06-14 15:14:40] local.DEBUG: Received request {"method":"GET","path":"/mcp/sse"} 
[2025-06-14 15:14:40] local.INFO: New SSE connection {"clientId":"sse_12800888fd13a8728e0a8d93373ebf15"} 
[2025-06-14 15:14:40] local.DEBUG: Sending SSE event {"event":"endpoint","frame":"event: endpoint
id: init-sse_12800888fd13a8728e0a8d93373ebf15
data: /mcp/message?clientId=sse_12800888fd13a8728e0a8d93373ebf15

"} 
[2025-06-14 15:14:40] local.INFO: Client connected {"clientId":"sse_12800888fd13a8728e0a8d93373ebf15"} 
[2025-06-14 15:14:40] local.DEBUG: Received request {"method":"POST","path":"/mcp/message"} 
[2025-06-14 15:14:40] local.DEBUG: Received message {"clientId":"sse_12800888fd13a8728e0a8d93373ebf15","frame":"{\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2025-03-26\",\"capabilities\":{},\"clientInfo\":{\"name\":\"laravel-mcp\",\"version\":\"1.0.0\"}},\"jsonrpc\":\"2.0\",\"id\":0}"} 
[2025-06-14 15:14:40] local.WARNING: Client requested unsupported protocol version: 2025-03-26 {"supportedVersions":["2024-11-05"]} 
[2025-06-14 15:14:40] local.DEBUG: Sending SSE event {"event":"message","frame":"event: message
data: {\"jsonrpc\":\"2.0\",\"id\":0,\"result\":{\"serverInfo\":{\"name\":\"Laravel MCP\",\"version\":\"1.0.0\"},\"protocolVersion\":\"2024-11-05\",\"capabilities\":{\"tools\":{\"listChanged\":true},\"resources\":{\"subscribe\":true,\"listChanged\":true},\"prompts\":{\"listChanged\":true},\"logging\":{}}}}

"} 
[2025-06-14 15:14:40] local.DEBUG: Sent response {"clientId":"sse_12800888fd13a8728e0a8d93373ebf15","frame":"{\"jsonrpc\":\"2.0\",\"id\":0,\"result\":{\"serverInfo\":{\"name\":\"Laravel MCP\",\"version\":\"1.0.0\"},\"protocolVersion\":\"2024-11-05\",\"capabilities\":{\"tools\":{\"listChanged\":true},\"resources\":{\"subscribe\":true,\"listChanged\":true},\"prompts\":{\"listChanged\":true},\"logging\":{}}}}
"} 
[2025-06-14 15:14:40] local.DEBUG: Received request {"method":"POST","path":"/mcp/message"} 
[2025-06-14 15:14:40] local.DEBUG: Received message {"clientId":"sse_12800888fd13a8728e0a8d93373ebf15","frame":"{\"method\":\"notifications/initialized\",\"jsonrpc\":\"2.0\"}"} 
[2025-06-14 15:14:40] local.DEBUG: Received request {"method":"POST","path":"/mcp/message"} 
[2025-06-14 15:14:40] local.DEBUG: Received message {"clientId":"sse_12800888fd13a8728e0a8d93373ebf15","frame":"{\"method\":\"ping\",\"jsonrpc\":\"2.0\",\"id\":1}"} 
[2025-06-14 15:14:40] local.DEBUG: Sending SSE event {"event":"message","frame":"event: message
data: {\"jsonrpc\":\"2.0\",\"id\":1,\"result\":[]}

"} 
[2025-06-14 15:14:40] local.DEBUG: Sent response {"clientId":"sse_12800888fd13a8728e0a8d93373ebf15","frame":"{\"jsonrpc\":\"2.0\",\"id\":1,\"result\":[]}
"} 
[2025-06-14 15:15:40] local.DEBUG: Received request {"method":"POST","path":"/mcp/message"} 
[2025-06-14 15:15:40] local.DEBUG: Received message {"clientId":"sse_12800888fd13a8728e0a8d93373ebf15","frame":"{\"jsonrpc\":\"2.0\",\"method\":\"notifications/cancelled\",\"params\":{\"requestId\":1,\"reason\":\"McpError: MCP error -32001: Request timed out\"}}"} 
[2025-06-14 15:15:40] local.DEBUG: MCP Processor caught McpServerException {"method":"notifications/cancelled","code":-32601,"message":"Method not found: MCP capability 'notifications' is not enabled on this server.","data":null} 

[CodeWithKyrian]

Hi, thanks so much for the detailed report and context.

1. Protocol Version Support

   The Laravel MCP server currently only supports 2024-11-05. Support for 2025-03-26 is actively in the works over in the base php-mcp/server package. That branch already includes most of the protocol updates, except for the OAuth flows, which are still pending. The core changes are solid and pretty far along.

   Right now, I’m wrapping up the test suite for that branch. I’m aiming to ship a release with 2025-03-26 support within the week. Once that’s out, the Laravel wrapper will be updated to depend on it, so if you can hold off till mid or end of the week, you should be able to upgrade and sync nicely with the newer AnythingLLM client.

2. notifications/cancelled Not Yet Supported

   This one isn’t wired up yet, unfortunately.

   Properly supporting notifications/cancelled means we need to track in-flight requests and hook them up to active operations, so they can be cleanly stopped on demand. It’s a bit more complex than the other notification methods. It’s definitely on the roadmap, just still figuring out the best way to build it without introducing too much stateful complexity.

   It’ll be more straightforward to handle in the dedicated server since it’s built on an async runtime and tracking cancellations there is cleaner. But for the integrated server, it gets trickier.

   I can’t guarantee it’ll land in the same release as the protocol update, but it’s high on the list for the next one....unless I find a clean solution sooner.

As for keeping the connection alive: while the MCP spec includes an optional ping mechanism to check if the other party is still responsive, it doesn’t actually suggest using it to prevent client-side timeouts or keep SSE connections alive. I did think about adding a proactive ping loop at first, but decided against it to stay closer to the spec. That said, we might offer it later as an opt-in if it proves useful. In general, most SSE clients already handle reconnection automatically, so dropped connections usually bounce back without much trouble.

Happy to hear any thoughts or suggestions you have around any of this.

[Jens-dev]

That’s fantastic news—thanks so much for the swift and thorough update! 🎉

We’re really excited to hear that MCP v2025‑03‑26 support is nearly ready and that the base php‑mcp/server branch is so far along. We’ll happily wait till later this week for the official release.

It also makes sense that notifications/cancelled support is being given the thought it deserves—it’s great to know it’s on the roadmap, even if it takes a bit longer to land.

Thanks again for the prompt response and clear direction.
Looking forward to upgrading and testing the new version as soon as it’s available!

[CodeWithKyrian]

The 2025-03-26 protocol version is now up and running 🚀 Feel free to test it out and share any feedback!