[nilslice]

you might like mcp.run, a tool management platform we're working on... totally agree running a process per tool, with all kinds of permissions is nonsensical - and the move to "remote MCP" is a good one!

but, we're taking it a step (or two) further, enabling you to dynamically build up a MCP server from other servers managed in your account with us.

try it out, or let me get you a demo! this goes for any casual comment readers too ;)

https://cal.com/team/dylibso/mcp.run-demo

[the_clarence]

I meant I wanted to run them synchronously in the same process :)

[nilslice]

that's what this does :)

you bundle mcp servers into a profile, which acts as a single virtual mcp server and can be dynamically updated without re-configuring your mcp client (e.g. claude)