I built freemcp.space — hosting for MCP servers, so you don't have to install them locally

Why I made it: Trying out an MCP server usually means npx/uv installing it on your own machine first, wiring up config, and hoping it runs. That's a lot of friction just to find out whether a server is useful to you. I wanted MCP servers to be remote and hosted by default — zero local setup.

What it does: Deploy and manage Model Context Protocol servers with zero infrastructure. You give it a Dockerfile or a GitHub repo, it builds and runs it in a container, and publishes it as a remote MCP endpoint at https://freemcp.space/{username}/{slug}/mcp. On the free plan a server sleeps after 15 minutes idle and wakes on demand in roughly 15 seconds. There are also 30-minute ephemeral sandboxes if you just want to poke at something, plus a public registry/marketplace of servers to browse.

Stack: Python 3.12, FastAPI, asyncpg (Aiven PostgreSQL), Redis, Docker + BuildKit, Caddy, Firebase Auth, SvelteKit frontend, Stripe, Hetzner Cloud. Hexagonal architecture, 55 migrations, 425+ tests.

Link: https://freemcp.space

Feedback / ideas welcome — especially on two things I keep going back and forth on: whether the platform's 13 MCP tools should stay in a single file, and whether the two separate transport implementations (stdio vs hosted SSE/HTTP) should be unified instead of maintained side by side.