MCP.Market

Floom MCP server

by floomhq·io.github.floomhq/floom·v0.1.6·46 stars
No reviews yet

Deploy Python functions as web apps with auto-generated UI, REST API, and shareable links.

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Growing

46 stars

Reviews

Write one

Nobody has reviewed Floom yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Floom tools (32, 11 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • create_from_templatewrite action

    Create a new Floom project from a starter template.

  • create_schedulewrite action

    Create a cron schedule that automatically runs an endpoint at specified intervals.

  • create_share_linkwrite action

    Create a public share link for a Floom endpoint. Share links allow anyone to run the endpoint without authentication.

  • delete_contextwrite action

    Remove a context entry from a Floom project.

  • delete_projectwrite action

    Delete a Floom project and all its data (versions, runs, secrets, storage).

  • delete_schedulewrite action

    Delete a cron schedule from a Floom project.

  • deploywrite action

    Deploy Python code to Floom and get a usable URL. Accepts raw Python source or a base64-encoded ZIP. Optionally include a floom.yaml config to declare endpoint schemas, secrets, and resource requirements.

  • deploy_from_githubwrite action

    Deploy a Floom app directly from a GitHub repository URL.

  • disable_share_link

    Disable a share link for a Floom project. The link will no longer be accessible.

  • disable_webhooks

    Disable public inbound webhooks for a Floom project.

  • enable_webhooks

    Enable public inbound webhooks for a Floom project. Once enabled, external services can trigger runs via POST /v1/webhooks/:slug/:action without authentication.

  • fetch_context

    Fetch external data from a URL and attach it as context to a Floom project. Context data enhances AI-powered endpoints.

  • get_context

    Retrieve stored context data for a Floom project.

  • get_logs

    Get recent run logs for a Floom project.

  • get_project

    Get details for a Floom project including endpoint schemas and input parameters. Use this before calling run to see what inputs an endpoint expects.

  • get_template

    Get details and code preview for a Floom starter template.

  • list_contexts

    List all context entries for a Floom project.

  • list_projects

    List all deployed Floom projects.

  • list_schedules

    List all cron schedules for a Floom project.

  • list_share_links

    List all share links for a Floom project.

  • list_templates

    List available starter templates for Floom projects.

  • list_versions

    List all versions of a Floom project. Shows which version is dev (latest deploy) and which is prod (promoted).

  • manage_secrets

    Manage secrets for a Floom project. Supports list, set, and delete operations.

  • promote

    Promote a version to production. By default promotes the current dev version. Runs a health check; auto-rolls back if the check fails.

  • refresh_context

    Re-fetch context data from its source URL.

  • rollback

    Rollback production to a previous version.

  • runwrite action

    Execute an action on a deployed Floom app. Preferred: use app_slug + action for simple invocation. Alternative: use project_id + endpoint_id + version_id for explicit control.

  • storage_deletewrite action

    Delete a stored value for a Floom project.

  • storage_get

    Retrieve a stored value for a Floom project.

  • storage_list

    List all stored keys for a Floom project with usage info.

  • storage_set

    Store a persistent key-value pair for a Floom project. Values persist across runs and deploys.

  • update_projectwrite action

    Update a Floom project name or slug.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 7 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Floom compares

Against every graded Developer tools MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 60% of 1,119 Developer tools servers
Tools
32
the typical Developer tools server has 7
Tools that change things
34%
typical: 5%. Fewer write tools means less an agent can break
GitHub stars
46
more than 91% of 855 Developer tools servers

What its tools let an agent do: 18 read · 3 create · 5 change · 3 delete · 3 run or deploy

Install Floom in Claude Code, Cursor or VS Code

Runs npx -y @floomhq/mcp-server on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add floom -- npx -y @floomhq/mcp-server
Add to Cursor

What the publisher says

From the Floom repository's README, as published. We do not edit it. Read it on GitHub

Floom

The loop engineering harness. AI workers that run on a loop.

Schedule them, trigger them, require approvals, and keep every run on the record. A worker is a folder: worker.yml + SKILL.md or run.py. Deploy it from Claude Code, Codex, or the CLI. Run it from the UI, REST, or MCP.

Get started · Build a worker · Try the hosted version · Read the docs

Most "AI automation" is a chat window you babysit, or a no-code graph that bills you per task and can't be audited. Floom is the loop engineering harness: a real runtime where a worker is a readable package, it runs on a loop without you watching, and every execution leaves logs, outputs, tool calls, approvals, and a replay you can trust. Used natively from Claude Code and Codex via MCP or CLI.

Deploy A Python Script As An App, REST API, And MCP Tool

Floom lets an agent or developer turn a Python script into a worker that non-developers can run from a UI, other systems can call through REST, and AI agents can operate through MCP.

Start with three files:

workers/my-worker/
  worker.yml
  run.py
  requirements.txt

Then validate, deploy, and run:

floom workers validate ./workers/my-worker
floom workers push ./workers/my-worker
floom run my-worker --input key=value

Read BUILDING.md for the full copy-paste worker contract.

What Floom Is: Worker Runtime For Background AI Workers

Floom turns repeatable knowledge-work automations into background AI workers. A worker can run manually, on a schedule, from a webhook, or from an app event. The runtime keeps the worker definition, input schema, output schema, logs, tool calls, approvals, and run history inspectable.

Use Floom when you want an AI agent to do recurring work without turning that work into an opaque chat thread, a hard-to-diff automation graph, or a one-off script with no supervision.

Build And Deploy An AI Worker From A Folder

AI agents and developers can build a Floom worker from a folder:

workers/<worker-id>/
  worker.yml        # manifest: inputs, outputs, trigger, runtime, secrets
  run.py            # script entrypoint, or SKILL.md for agent mode
  requirements.txt  # optional Python dependencies

Deploy the worker with:

floom workers validate ./workers/<worker-id>
floom workers push ./workers/<worker-id>
floom run <worker-id> --input key=value

After deployment, Floom exposes the worker in the UI, through REST endpoints, and through the Floom MCP server for AI clients. For the complete copy-paste build contract, read BUILDING.md.

What A Worker Looks Like

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Floom: common questions

Is Floom MCP server safe?
Mostly: it is graded B (82/100). Read the Floom safety report
How do I install Floom?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Floom need an API key?
Yes. The registry entry asks for FLOOM_API_KEY.
Is Floom maintained?
The last commit was 44 days ago (2026-09-21). The latest release is v0.1.6.
What can I use instead of Floom?
Servers from other publishers that do the same job: Aiven MCP server, Dockhold MCP server and Scrapling MCP Server.
How does Floom compare with other Developer tools MCP servers?
safety score 82/100 (higher than 60% of 1,119 Developer tools servers); tools 32 (the typical Developer tools server has 7); tools that change things 34% (typical: 5%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Floom

Same job from other publishers: the closest match first, then the best rated.

  • Aiven MCP
    Provision PostgreSQL, manage Apache Kafka, and deploy apps with Aiven - all from your AI assistant.
    A
  • Dockhold
    Deploy your project to a live HTTPS URL from your AI tool; read logs, set variables, resize apps.
    A
  • Scrapling MCP Server
    Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
    A
  • walkerOS Flow
    Build, validate, simulate, and deploy walkerOS event pipelines
    B
  • Omnara
    Deploy durable AI agents with Omnara, an open-source managed-agent platform.
    A