Floom

What is Floom?

Floom is an open‑source protocol and runtime for agentic work. It turns an OpenAPI specification into three surfaces: a shareable web form, an MCP server that an agent can call, and an HTTP API endpoint — all with built‑in auth, rate limits, secret injection, and run history.

How to use Floom?

Point Floom at an OpenAPI spec URL. For the cloud version, sign in at floom.dev and publish via the build page. For self‑hosting, create an apps.yaml manifest and run the official Docker image with docker run; the manifest defines proxied (wrapping an existing API) or hosted (Floom runs your container) modes. Every published app is immediately available as a web form at /p/:slug, an MCP endpoint at /mcp/app/:slug, and an HTTP endpoint at /api/:slug/run.

Key features of Floom

• One manifest generates a web form, MCP server, and HTTP API.
• Proxied mode wraps any existing API; hosted mode runs your Docker container.
• Built‑in Bearer/API‑key auth, per‑operation rate limits, and secret injection.
• Every app exposes MCP tools; four MCP admin tools let an agent add new apps.
• Shareable result URLs and run history are included out of the box.

Use cases of Floom

• Vibecoder creators – paste an OpenAPI URL and instantly publish a shareable web form plus an MCP tool for friends.
• Biz users – wrap an internal API (e.g. Stripe) in a form for ops teams, with logged runs and clean output rendering.
• Agent development – use Floom’s MCP server so an AI agent can call your API without custom glue code.
• Self‑hosted API gateways – run Floom in Docker to manage rate limits, auth, and logs for your own services.

FAQ from Floom

What input formats does Floom support?

Floom accepts an OpenAPI specification (URL or local file). It reads each operation and automatically turns parameters into form fields or MCP tool inputs.

How does Floom handle authentication and rate limiting?

Floom supports Bearer/API‑key authentication and per‑operation rate limits. Secrets are injected at runtime from environment variables or a config file.

Can I self‑host Floom?

Yes. Self‑hosting takes about 60 seconds: write an apps.yaml manifest and run the official Docker image (ghcr.io/floomhq/floom-monorepo). The full guide is in docs/SELF_HOST.md.

What are the two operation modes (proxied vs. hosted)?

In proxied mode Floom wraps an existing API by reading its OpenAPI spec. In hosted mode Floom runs your own container, using a runtime, build, and run directive in the manifest.

Does Floom expose MCP tools for agents?

Yes. Every published app automatically provides MCP tools. Additionally, four MCP admin tools (ingest_app, list_apps, search_apps, get_app) let an agent add and manage apps over MCP.