Floom runs on your own machine — the client starts it, so there is no endpoint to ping. 36 installs a week from npm. Last commit 2 Oct 2026.
Deploy Python functions as web apps with auto-generated UI, REST API, and shareable links.
We read the source, 5 d ago · rules 995398eba69f
A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.
proc = subprocess.run(
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
result = subprocess.run(
backup_path = os.path.join(
backup_dir, f"floom-preclear-{time.time_ns()}.db"
)
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
That is not a flaw by itself — but it is where things go wrong when it is not the job. We re-read this code on every release. Watch it and you hear from us the day another one appears.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add floom -e 'FLOOM_BASE_URL=<FLOOM_BASE_URL>' -e 'FLOOM_API_KEY=<FLOOM_API_KEY>' -- npx -y @floomhq/mcp-server
{
"mcpServers": {
"floom": {
"command": "npx",
"args": [
"-y",
"@floomhq/mcp-server"
],
"env": {
"FLOOM_API_KEY": "<FLOOM_API_KEY>",
"FLOOM_BASE_URL": "<FLOOM_BASE_URL>"
}
}
}
}
[mcp_servers.floom]
command = "npx"
args = ["-y", "@floomhq/mcp-server"]
env = { FLOOM_BASE_URL = "<FLOOM_BASE_URL>", FLOOM_API_KEY = "<FLOOM_API_KEY>" }
{
"mcpServers": {
"floom": {
"command": "npx",
"args": [
"-y",
"@floomhq/mcp-server"
],
"env": {
"FLOOM_API_KEY": "<FLOOM_API_KEY>",
"FLOOM_BASE_URL": "<FLOOM_BASE_URL>"
}
}
}
}
{
"servers": {
"floom": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@floomhq/mcp-server"
],
"env": {
"FLOOM_API_KEY": "<FLOOM_API_KEY>",
"FLOOM_BASE_URL": "<FLOOM_BASE_URL>"
}
}
}
}
Put your own values in place of
<FLOOM_BASE_URL> (Base URL of the Floom control plane), <FLOOM_API_KEY> (API key for authenticating with Floom).
The author’s registry entry marks them as required.
Research, build, and deploy AI-generated websites via the Warpweb API.
Deploy and manage web apps with Atlas hosting, isolated Postgres, file storage and logs.
Deploy web apps with sign-in, per-user storage, realtime and AI built in.
Deploy full-stack web apps with database, file storage, auth, and RBAC via a single API call.
Give your AI a place to publish: living pages with live data, shareable links, no deploy pipeline.
Deploy and share small apps with team login, persistent data, versioned updates and domains.
Deploy a web game to a playable multiplayer URL with rooms, state sync, and leaderboards.
Deploy apps from GitHub, read build/runtime logs, and manage your app's users from your AI agent.
Answers built from our own checks of this server.