The open-source, self-hosted runtime for AI workers. Sandboxed by default.
Floom MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. The open-source, self-hosted runtime for AI workers. Sandboxed by default.
The loop engineering harness. AI workers that run on a loop.
Floom is an open-source runtime for background AI workers that run from versioned worker folders with declared inputs, outputs, triggers, tools, approvals, logs, REST API access, UI access, and MCP access.
Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.
Once Floom is connected, these are the calls the assistant has available:
Runtime — cron, shell, or local processIsolation — runs on your hostObservability — scrollback, if anyHosting — your hostYou will need 2 environment variables: E2B_API_KEY, FLOOM_SECRET. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Plenty of monitoring and observability servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Floom's toolset — Runtime, Isolation, Observability and 1 more — is a fair guide to whether it matches your workflow. It is maintained by floomhq; worth a glance at recent repository activity before you build anything load-bearing on it.
We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.
| Tool | What it does |
|---|---|
| Runtime | cron, shell, or local process |
| Isolation | runs on your host |
| Observability | scrollback, if any |
| Hosting | your host |
{
"mcpServers": {
"floom": {
"command": "npx",
"args": ["-y", "@floomhq/floom"],
"env": {
"E2B_API_KEY": "your-value",
"FLOOM_SECRET": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| E2B_API_KEY | Credential the server authenticates with. | Yes |
| FLOOM_SECRET | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.