The idea is simple: Wouldn’t it be cool to ask a website what it does — without clicking, searching, or guessing?
That’s exactly what MCP is great for. But MCP servers need to be installed — and that’s a hassle.
So why not have one MCP proxy that connects to multiple MCP-enabled websites (or services)? That’s what we’re building: an MCP proxy that brings it all together.
But the proxy is only half the story. How do you make your website speak MCP — easily?
That’s where MCPHosting comes in.
A simple way to define your MCP server declaratively — and host it here.
This is still under development. A few websites are already using it, but it’s not public yet.
Want to try it out or collaborate?