Our team at Bramble (YC F24) has been messing around with tool-using agents lately. We ran into some friction trying to use Anthropic’s Model Context Protocol (MCP):
- Most MCP servers are stdio-based, but we wanted something HTTP-friendly
- We needed auth and the ability to run servers remotely
- We couldn’t find a hosted option to just try the thing without spinning up infra. We have a bunch of different automations that could be valuable for our ops, but there's no way to know how doable each one is without experimenting with available APIs integrated into our LLM calls.
This all seemed a bit too much to chew through for every integration we wanted to try, so we threw together https://mcpverse.dev — a one-click way to spin up hosted MCP servers with auth baked in. No server setup, free to use, and made for folks who want to experiment with agents without spending half the day wiring stuff up.
At the moment we’re just using the underlying infra to test and run some internal automations, but we’ve opened up options for folks to request additional MCP server support for more integration options.
Currently on the roadmap:
- We’re working on Google Workspace, which is a huge want but is trickier than most because it essentially requires OAuth support
- CLI tool or API to help spin up new servers at scale
- Integrate proxy for existing MCP clients that only support stdio
- Maybe some client tooling (clients are still pretty tricky to write, and we have 2-3 more use cases we want to build client logic for)
Hopefully helpful to someone else trying to avoid yak-shaving. Would love feedback (you can email us directly at team@mcpverse.dev)!
Using this with Slack + DBs is really easy! It's still a bit finicky to do reliably recurring workflows, but hoping that'll become easier as we improve our client implementation.
2 comments
[ 3.2 ms ] story [ 14.4 ms ] thread- Most MCP servers are stdio-based, but we wanted something HTTP-friendly - We needed auth and the ability to run servers remotely - We couldn’t find a hosted option to just try the thing without spinning up infra. We have a bunch of different automations that could be valuable for our ops, but there's no way to know how doable each one is without experimenting with available APIs integrated into our LLM calls.
This all seemed a bit too much to chew through for every integration we wanted to try, so we threw together https://mcpverse.dev — a one-click way to spin up hosted MCP servers with auth baked in. No server setup, free to use, and made for folks who want to experiment with agents without spending half the day wiring stuff up.
At the moment we’re just using the underlying infra to test and run some internal automations, but we’ve opened up options for folks to request additional MCP server support for more integration options.
Currently on the roadmap: - We’re working on Google Workspace, which is a huge want but is trickier than most because it essentially requires OAuth support - CLI tool or API to help spin up new servers at scale - Integrate proxy for existing MCP clients that only support stdio - Maybe some client tooling (clients are still pretty tricky to write, and we have 2-3 more use cases we want to build client logic for)
Hopefully helpful to someone else trying to avoid yak-shaving. Would love feedback (you can email us directly at team@mcpverse.dev)!