跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
部署与云服务

webflow-mcp:cloud-apps

Create GitHub-source Webflow Cloud apps and monitor, troubleshoot, or manage existing apps through Webflow MCP. Use when creating a standalone or site-attached app from GitHub; identifying apps or environments; checking public URLs, domains, configuration keys, or deployed versions; diagnosing failures; changing a GitHub source, branch, or mount; provisioning environments; or previewing a deployment, retry, or rollback. Do not use for Designer/CSS variables, CLI/local-source app creation or deployment, or passing environment-variable values through MCP.

webflow · 已有 AI 审核记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add webflow/webflow-skills --skill webflow-mcp:cloud-apps

技能说明


name: webflow-mcp:cloud-apps description: Create GitHub-source Webflow Cloud apps and monitor, troubleshoot, or manage existing apps through Webflow MCP. Use when creating a standalone or site-attached app from GitHub; identifying apps or environments; checking public URLs, domains, configuration keys, or deployed versions; diagnosing failures; changing a GitHub source, branch, or mount; provisioning environments; or previewing a deployment, retry, or rollback. Do not use for Designer/CSS variables, CLI/local-source app creation or deployment, or passing environment-variable values through MCP.

Webflow Cloud Apps

Use data_apps_tool to create GitHub-source apps, answer operational questions, and manage environments for Webflow Cloud apps. Start from the user's outcome, gather only the evidence needed, and distinguish observations from conclusions.

Use the webflow-cli:cloud skill when the task requires CLI/local-source app creation or deployment, or creating or updating environment variables. Client-side build output is not sent to Webflow and cannot be recovered through MCP.

Instructions

1. Establish scope

  1. Call webflow_guide_tool before any other Webflow MCP tool. The live guide and action schemas are authoritative for current arguments and responses.
  2. Use Webflow MCP tools for Webflow operations except the explicit CLI handoff for environment-variable values. Never call Webflow APIs directly.
  3. Include the required context parameter in every tool call. Write 15-25 words in third-person perspective.
  4. Route by the capability the task requires:
    • Use data_apps_tool to create GitHub-source apps; inspect apps, environments, domains, deployment records, logs, and variable metadata; manage GitHub sources and environments; and enqueue GitHub deployments.
    • Use data_variable_tool for Designer color, size, font, and CSS variables.
    • Use webflow-cli:cloud for CLI/local-source apps, local builds and deployments, or creating and updating environment-variable values.
  5. If data_apps_tool is unavailable, report that the Cloud Apps MCP capability is not enabled. Do not bypass it with a direct API request.

Never ask the user to paste an environment-variable value or secret into chat. For a create or update, delegate to webflow-cli:cloud and require a hidden prompt, stdin, or protected file. Never pass a secret as a positional argument.

2. Resolve the target

Discover identifiers in this order:

list_apps -> app_id
list_environments(app_id) -> env_id
list_deployments(app_id, env_id) -> deployment_id

App names are unique only within a site, so resolve a named app with site_id + name. If multiple resources match, present distinguishing metadata and require the user to select one before any mutation. Use the live guide for filter, pagination, cursor, and action-batching mechanics.

3. Follow the matching user story

Create a GitHub-source app

  1. Establish the app name, canonical GitHub repository URL, branch, optional description, and whether it is standalone or attached to an existing site.
  2. For a site-attached app, resolve the site ID. Omit site_id for standalone.
  3. Apply the mount contract before previewing:
    • A standalone app always mounts at /; omit mount or use /.
    • A site-attached app defaults to /app, rejects /, and requires a valid non-root mount when overriding the default.
  4. Explain that standalone creation requires a workspace-scoped user token. Webflow derives the GitHub installation and validates repository access; do not request an installation ID.
  5. Call create_app with its default dry run. Show the repository, branch, attachment, site when applicable, mount, and initial-deployment attempt.
  6. Require confirm. Immediately after confirmation and before execution, record the start time and generate one stable idempotency_key; execute with dry_run: false, then record the completion time. Reuse that key only for exact retries of this creation.
  7. Treat creation and initial deployment as separate outcomes. A returned app means creation succeeded even if deployStatus is skipped or failed. For triggered, inspect the environment and deployment; for skipped, check the branch or push a commit; for failed, preserve the app and inspect or retry deployment separately.
  8. If the app or outcome is unreadable, reconcile before retrying:
    • For a site-attached app, collect candidates with site_id + name; for a standalone app, collect candidates by name.
    • In both cases, compare each candidate's name, sourceUrl, and createdAt with the requested repository and recorded execution window.
    • Continue to environments and deployments only when exactly one candidate matches. Do not retry while the created app remains ambiguous.
  9. Never delete a created app automatically because deployment failed. Do not treat an initial deployment dashboard link as the environment's public URL.

Which app and environment am I looking at?

  1. Use list_apps to find the app and get_app for its metadata, including sourceUrl and siteAttached.
  2. Use list_environments to report the branch, mount, publicUrl, and latest deployment status. If publicUrl is null, report that no user-facing environment address is available; do not construct one.
  3. Use get_app_domains when the user asks where the app is reachable.
  4. Explain that custom-domain results exclude the default *.webflow.io hostname. Domains for an app attached to a regular Webflow site may belong to the parent site and be shared by sibling apps.

What is deployed, and is it healthy?

  1. Use list_environments for the environment's latest deployment status.
  2. Use list_deployments, newest first, then get_deployment for the selected deployment's detailed timeline and version metadata.
  3. Treat starting, `buil
阅读完整来源 ↗