Migrate project to `xmcp`

[mmmeff]

xmcp seems like a much saner developer experience over using the @modelcontextprotocol/sdk directly.

Let's migrate!

https://xmcp.dev/

[thegreyfellow]

I am looking into this. Also thanks a lot for the great work on this clean MCP server implementation. May I ask why xmcp and not stick with the standard sdk ?

[mmmeff]

This ticket is more of a dev spike then a hard-set plan to migrate, but I find the standard MCP SDK to be fairly cumbersome to develop with - it's too low-level.

Switching to a framework like XMCP looks like it'd cut down on a lot of bespoke code in this project while simultaneously making it easier/cheaper to keep up to date with the ever changing MCP specifications.

Just switching from SSE to SHTTP was a huge refactoring effort. Any framework with decent enough abstractions around each tool should make supporting new protocols or specification changes as easy as updating to the latest version of the framework. Leaning on those abstractions means we can delete the abstractions in our own codebase (like the ToolLibrary system here) and have less overall LoC to maintain.

[thegreyfellow]

I fully agree, it makes total sense. I will have a look at xmcp when possible 👌