Docs navigation
Docs
Get started with foro.sh
foro.sh takes an MCP server from a Git repo - read straight from the pyproject.toml or package.json it already has - to a cloud-deployed, publicly reachable URL. Every server gets its own isolated container on sovereign EU infrastructure, and there's nothing for you to operate yourself.
Deploy your first server
Sign in with GitHub, pick a repo, add secrets - live in about a minute.
Connect an agent
Add your server URL to Claude, Cursor, or any MCP client.
Check what fits
Five shapes of MCP server that fit cleanly, and where the edges are.
Get started
- Quickstart - From a Git repo to a live MCP server URL in about a minute.
- Project config - What foro reads from your pyproject.toml or package.json, and what [tool.foro] can override.
Deploy
- Build pipeline - How a repo becomes a running container, and what the build log shows.
- Secrets - Encrypted at rest, injected at container start, never in build logs.
- Deploy & build logs - Live streams during a deploy, and persisted history by plan.
Use your server
- Connect an agent - Add your server URL to Claude, Cursor, or any MCP client.
- Authentication - The per-project bearer token every deployed server starts with, and the other auth modes a project can switch to.
- Playground & chat - Call tools directly from the dashboard and inspect raw responses.
- MCP Apps - Return UI, not just JSON: a ui:// resource several tools drive, rendered sandboxed.
- Data protection - How PII scrubbing masks emails, IBANs, names, and more in tool-call results before they reach an LLM.
- Custom domains - Serve your server on a domain you own, verified over DNS with automatic TLS.
Platform
- Isolation & networking - One container and one private network per project, by construction.
- EU data residency - A fully European cloud - no non-EU parent, no non-EU cloud in the request path.
- Security specifications - Bearer-token auth, container sandboxing, encrypted secrets, and metadata-only tracing, each backed by the file that enforces it.
- Quotas & limits - Project and container limits in v0, and what happens at the ceiling.
- Tokens - How foro counts tokens: the schema an LLM loads, and what each call costs.
Guides
- What fits on foro.sh - Five shapes of MCP server that fit foro.sh, and a dedicated guide for each.
- Read-only API wrapper - Wrap one upstream API in a few tools - the simplest shape an MCP server takes.
- Stateful MCP tools - Deploy an MCP server that remembers what an earlier call wrote down.
- Internal MCP connectors - Point an agent at company data that has to stay inside the company.
- Personal MCP automation - One person, several devices, a handful of tools that take actions.
- Dev-tool MCP servers - Wrap your own tooling - CI, deploys, error rates - so an agent can use it too.