problems we're hoping to solve:
- Many people are creating MCP servers for the same apps. They're scattered across different repos but flavors of the same thing. We're making one standardized mono project for all MCP servers.
- Startups are charging for hosting MCP servers. This is blocking tons of people from being able to play around with MCP casually. We're hosting them for free.
- Non-technical people should be able to use MCP without needing to learn how to clone a repo and set up a venv. We're trying to enable a one click integration if people want to use the free hosted service.
The plan is to keep contributing until we have an MCP server for basically every useful app anyone could want.
I built https://skeet.build/mcp where anyone can try out mcp for cursor and dev tools.
We did this because of a painpoint I experienced as an engineer having to deal with crummy mcp setup, lack of support you have no idea how hard it is to set up SSE, deal with API keys and scope issues, and then to find things like the tool that you want isn’t even coded yet.
And so one of the areas we found it to be useful was to do the soft communications with tools like Jira linear slack - updating stakeholders and all that friction that engineers hate doing. Some other areas people use a lot of tools with sequential thinking
Mostly for workflows that I like:
* start a PR with a summary of what I just did * slack or comment to linear/Jira with a summary of what I pushed * pull this issue from sentry and fix it * Find a bug a create a linear issue to fix it * pull this linear issue and do a first pass * pull in this Notion doc with a PRD then create an API reference for it based on this code * Postgres or MySQL schemas for rapid model development
Everyone seems to go for the hype but ease of use, practical pragmatic developer workflows, and high quality polished mcp servers are what we’re focused on
Lmk what you think!
Currently working on a desktop app so everything runs on a native Mac app!
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.
Would something like https://github.com/OpenAdaptAI/OmniMCP make sense to include here?
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.
Seems like everything I find requires running locally or hosting your own instance.
I built https://skeet.build/mcp where anyone can try out mcp for cursor and dev tools.
We did this because of a painpoint I experienced as an engineer having to deal with crummy mcp setup, lack of support you have no idea how hard it is to set up SSE, deal with API keys and scope issues, and then to find things like the tool that you want isn’t even coded yet.
And so one of the areas we found it to be useful was to do the soft communications with tools like Jira linear slack - updating stakeholders and all that friction that engineers hate doing. Some other areas people use a lot of tools with sequential thinking
Mostly for workflows that I like:
* start a PR with a summary of what I just did * slack or comment to linear/Jira with a summary of what I pushed * pull this issue from sentry and fix it * Find a bug a create a linear issue to fix it * pull this linear issue and do a first pass * pull in this Notion doc with a PRD then create an API reference for it based on this code * Postgres or MySQL schemas for rapid model development
Everyone seems to go for the hype but ease of use, practical pragmatic developer workflows, and high quality polished mcp servers are what we’re focused on
Lmk what you think!
I chose wasm for package format. so everyone can choose the programming language they are familiar with. caveat: rust still has best support for wasm. everything else is hit or miss.
I chose OCI registry for package publishing because that's what everyone already has in their infrastructure. or just use dockerhub/GHCR.
This is the simplest way I know of to get started with it.
obligatory https://xkcd.com/927/