Server facts
floom MCP Server
Project
- Author
- floomhq
- Repository
- github.com/floomhq/floom
- License
- Not specified
- Category
- MCP Gateways & Proxies
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 46
- Last commit
- Data as of
Overview
Floom gives app creators and internal operations teams ways to publish API-backed workflows for people and agents. An OpenAPI definition supplies the inputs for a browser form, an MCP interface, and an HTTP endpoint. Apps can proxy an existing service or run in a Docker container managed by Floom. The deployment tools also accept Python source, ZIP packages, or a GitHub repository, while template tools let users inspect starter code and create projects from it. Before executing an action, users can inspect a project's endpoint schemas and expected parameters.
Project operations include persistent secret management, per-run secret inputs, stored key-value data, and recent execution logs. Version tools distinguish development deployments from production, support promotion with a health check, and allow production rollback. Context tools fetch external URL data, retrieve saved content, and refresh it from its source. Cron schedules can invoke endpoints at intervals. Public share links and inbound webhooks provide unauthenticated execution paths, with separate controls to disable them. Other tools list or rename projects and delete a project together with its associated data.
floom setup notes
- floom records stdio only; confirm a network transport upstream before planning remote access.
- floom has no recorded license; confirm reuse terms in its repository.