Webflow MCP Server

The Webflow MCP Server bridges the gap between AI assistants and the powerful, visual‑centric CMS that is Webflow. By exposing Webflow’s RESTful API as a set of intuitive tools, Claude can query site metadata, inspect publishing status, and retrieve locale configurations—all without leaving the chat. This eliminates the need for developers to manually run API calls or navigate the Webflow dashboard, streamlining workflows that involve site audits, content strategy discussions, or automated reporting.

At its core, the server offers two straightforward yet valuable operations: and . The first lists every site the authenticated user can access, providing a rich set of details such as display names, workspace IDs, creation and publishing timestamps, preview URLs, time‑zone settings, custom domain information, locale configurations, and data‑collection flags. The second tool drills down into a single site by its ID, returning the same comprehensive snapshot for targeted analysis. These tools empower developers to quickly assess site health, verify deployment pipelines, or generate compliance reports directly from the assistant’s interface.

Key capabilities of this MCP server include:

• Secure authentication via Webflow API tokens or OAuth, ensuring that only authorized users can access sensitive site data.
• Rich type definitions for sites, custom domains, and locales, giving developers confidence that the responses are predictable and type‑safe.
• Robust error handling for common pitfalls such as missing or invalid tokens, with clear guidance on troubleshooting steps.
• Seamless integration into Claude Desktop through the Smithery CLI, allowing instant installation and configuration without manual scripting.

Real‑world scenarios that benefit from this server are plentiful. A front‑end engineer can ask Claude, “Which of my Webflow sites has the most recent publication date?” and receive an instant answer that includes the preview link. A content strategist might request a list of all sites where data collection is disabled, enabling quick compliance checks. A DevOps team could embed these tools into a broader CI/CD pipeline, using the assistant to verify that deployment triggers align with the correct workspace or locale settings.

Because the server exposes only read‑only operations, it presents a low‑risk integration path. Developers can incorporate these tools into multi‑step prompts—for example, first retrieving a site list, then prompting the assistant to draft an email summarizing publishing trends. The combination of straightforward API wrappers and Claude’s conversational interface turns routine CMS queries into an interactive, context‑aware experience that saves time and reduces friction across the entire development lifecycle.