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.
@floomhq
基本情報
概要はまだありません
以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。
{
"mcpServers": {
"floom": {
"command": "npx",
"args": [
"-y",
"@floomhq/mcp-server"
]
}
}
}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. If your code makes HTTP requests (requests, httpx, urllib), set config.network to true. Without it, outbound network access is blocked.
Execute an action on a deployed Floom app. Returns the function output as JSON. Preferred: use app_slug + action for simple invocation. Alternative: use project_id + endpoint_id + version_id for explicit control. Pass secrets: {KEY: value} for functions that require API keys.
List all deployed Floom projects.
Get details for a Floom project including endpoint schemas and input parameters. Use this before calling run to see what inputs an endpoint expects.
Manage persistent secrets (API keys, tokens) for a Floom project. Available across all runs. Supports list, set, and delete operations. For one-time secrets, use the secrets parameter on the run tool instead.
Get recent run logs for a Floom project.
List all versions of a Floom project. Shows which version is dev (latest deploy) and which is prod (promoted).
Promote a version to production. By default promotes the current dev version. Runs a health check; auto-rolls back if the check fails.
Rollback production to a previous version.
Store a persistent key-value pair for a Floom project. Values persist across runs and deploys.
Retrieve a stored value for a Floom project.
Delete a stored value for a Floom project.
List all stored keys for a Floom project with usage info.
Create a public share link for a Floom endpoint. Share links allow anyone to run the endpoint without authentication.
List all share links for a Floom project.
Disable a share link for a Floom project. The link will no longer be accessible.
Fetch external data from a URL and attach it as context to a Floom project. Context data enhances AI-powered endpoints.
List all context entries for a Floom project.
Remove a context entry from a Floom project.
Delete a Floom project and all its data (versions, runs, secrets, storage).
Update a Floom project name or slug.
Deploy a Floom app directly from a GitHub repository URL.
List available starter templates for Floom projects.
Get details and code preview for a Floom starter template.
Create a new Floom project from a starter template.
Retrieve stored context data for a Floom project.
Re-fetch context data from its source URL.
Create a cron schedule that automatically runs an endpoint at specified intervals.
List all cron schedules for a Floom project.
Delete a cron schedule from a Floom project.
Enable public inbound webhooks for a Floom project. Once enabled, external services can trigger runs via POST /v1/webhooks/:slug/:action without authentication.
Disable public inbound webhooks for a Floom project.
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.
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.
Floom accepts an OpenAPI specification (URL or local file). It reads each operation and automatically turns parameters into form fields or MCP tool inputs.
Floom supports Bearer/API‑key authentication and per‑operation rate limits. Secrets are injected at runtime from environment variables or a config file.
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`.
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.
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.
PickFu MCP is a Model Context Protocol (MCP) server that connects AI assistants, developers, marketers, product managers, and AI agents to PickFu's consumer research platform. It enables users to create surveys, conduct

DeepMark helps teachers deliver rapid, consistent marking with meaningful feedback for every student — in a fraction of the time. What once took a week, now takes one free period.

Model Context Protocol Servers

Connect your AI assistant to your own YOUB endurance training account. Read recorded activities with full analysis, planned sessions, race goals, wellness (HRV, sleep, resting HR) and your athletic profile. Create or mov

Yuppsy MCP: build and publish real estate websites from your AI assistant. Yuppsy lets your AI assistant create live websites for real estate agents and individual property listings. You don't need a designer or any code
コメント