Just a couple of things that I think makes GuMCP different than other options out there:
- Having a unified way to run each server via stdio and sse. Basically all existing providers either let you connect through their hosted sse service or let you clone and run stdio locally. Rarely is there a very simple way to do either/or, especially when it comes to hosting your own sse server out-of-the-box. Existing options like Zapier's MCP are closed source, so it's not so simple.
- Setting a flexible and generic framework for integration auth with MCP servers. Currently, methods of authentication vary from server to server. We provide a unified mechanism of auth for every single server that is importantly generic enough for you to be able to host it on your own. We do this through having a base 'AuthClient' that is used across each of our servers, which supports any arbitrary implementation. For local use, we provide a LocalAuthClient that sets a standard for integrations, OAuth and otherwise.
- We also have a GumloopAuthClient that uses your existing credentials for Gumloop, which will then exact similarly to how Zapier or Composio do their MCP servers, with auth taken care of easily. Difference is you have the flexibility to also host it on your own with your own AuthClient, or run locally with stdio and local auth as well.
- Ready-to-deploy sse through one URL. If you want to host on your own, the repository out-of-the box can be deployed with ALL sse servers hosted under a single URL.
- For open source contributions, your server will be deployed and hosted instantly. No need to fiddle with devops to get a SSE server available remotely for your implementation. This makes it way simpler for less technical folks (or just those who don't want to deal with infra) to make their ideas a reality.
Flowise https://flowiseai.com/ does something similar as well! I would check them out for sure if you're looking more on the OSS side.
We had the core node logic open source at one point, but closed it because we weren't seeing many contributions and it was less overhead once we started implementing things like node versioning, integrations, credentials, etc.
We still do deploy on-prem for enterprises that need it secure on their own cloud, and will link into open-sourcing a self-hosted version in the futur efor sure!
I think this is a good complement for use WITH guMCP rather than having it in the core repo itself, definitely will be playing around with this.