@floopfloop/mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOOP_API_KEY | Yes | Your FloopFloop API key. Required to authenticate with the FloopFloop API. | |
| FLOOP_API_URL | No | Optional override for the FloopFloop API URL (e.g., to point at staging). | https://api.floopfloop.com |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsA | List all FloopFloop projects the authenticated user has access to. Optionally scope to a team. |
| get_projectA | Fetch a single project by id or subdomain. Returns the project's url, status, and metadata. |
| project_statusA | Fetch the current build/deploy status for a project. Cheap — safe to call in a polling loop. |
| create_projectA | Create a new FloopFloop project from a natural-language prompt. Build kicks off immediately. Call wait_for_live to block until the site is up, or poll project_status. |
| refine_projectA | Send a refinement message to an existing project. Triggers a follow-up build unless the backend decides it's a code-only edit. |
| wait_for_liveA | Block (polling every 2 s) until the project reaches a terminal state. Returns the final Project on success, an error result on build-failed or build-cancelled. |
| check_subdomainA | Check whether a given subdomain slug is free. |
| suggest_subdomainB | Ask the backend to generate a friendly subdomain slug based on a natural-language prompt. |
| list_secretsA | List secret keys for a project. Values are never returned — only names, because FloopFloop stores secrets one-way-encrypted. |
| set_secretB | Create or overwrite an environment secret on a project. |
| remove_secretA | Delete a secret from a project. |
| whoamiA | Return the current user's id, email, and plan. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool targets a distinct resource (project, secret, subdomain) with clear actions. No overlap: check_subdomain vs suggest_subdomain are separate operations, and wait_for_live complements create_project without ambiguity.
Tools mostly follow verb_noun pattern (e.g., create_project, remove_secret, list_projects). whoami is a mild deviation but is a common convention. Minor inconsistency: project_status is noun-based while others are verb-based.
12 tools is well-scoped for a project management MCP. Each tool covers a necessary operation without bloat, from project CRUD to secret and subdomain management.
Covers core project lifecycle (create, get, list, refine, status) and secret management (list, set, remove). Missing update_project (rename) or delete_project, but these might be intentional gaps for safety.