Intro
provide context, tools, and prompts to clients
Hey you, you're finally awake.
It's 2025,
and we've been able to Move on to ESM-only,
built on Web Standards and Standard Schema...
No, wait, why are there CommonJS, Zod, AJV and Express?
If you don't want to see that either, then xsMCP is for you.
Independent implementation
xsMCP does not depend on @modelcontextprotocol/sdk, but reimplement with reference to it.
This allows us to significantly reduce the size.
Client/Server Code Separation
Usually you should only want to use one of them.
If you wish to use both, don't worry, just install them together.
Modern target, Runtime-agnostic, Schema library-agnostic
xsMCP is built as ES Module for the ESNext target.
We try not to rely on Node.js built-in modules wherever possible, so it works well in the browser, Deno, Bun, and edge runtimes.
For the server, we currently have the following modules: