feat: @gensx/mcp

[jmoseley]

Proposed changes

Add a new package, @gensx/mcp, that enables the creation of MCP contexts with a provider and a useContext helper. This provider manages the lifecycle of the server (spinning it up and shutting it down).

One thing that was required to make this work that I'm not super stoked about: Needed to add an onComplete to the Provider interface, so that we can perform tasks after the children of a provider have full resolved. This is necessary for us to close the connection (aka shutdown) the MCP server once that part of the workflow has finished.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
gensx-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 28, 2025 6:53pm
gensx-home	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Feb 28, 2025 6:53pm

[EvanBoyle]

One thing that was required to make this work that I'm not super stoked about: Needed to add an onComplete to the Provider interface, so that we can perform tasks after the children of a provider have full resolved. This is necessary for us to close the connection (aka shutdown) the MCP server once that part of the workflow has finished.

Can we handle the lifecycle via node.js process hooks? This thing is a singleton across the node process, so can we just add a process.on(exit, ...) handler? (maybe other hooks/handler we need to attach to as well...).

[jmoseley]

@EvanBoyle I tidied this up, but opted to keep the onComplete functionality. However, I did add support for passing a pre-connected Client, so that the developer has the option to manage the lifecycle themselves if they like.