Webflow Service Interface Module

This Micro-Control-Plane (MCP) server allows Claude agents to interface directly with the backend services exposed by Webflow.

Essential Prerequisites

To ensure smooth operation, the following components are mandatory:

• Runtime Environment: Node.js (version 16 or newer is required)
• Client Application: Claude Desktop Application instance
• Platform Access: Active Webflow Account Credentials
• Authorization Credential: A valid Webflow API Token (either a Site-scoped token or an OAuth 2.0 Access Token)

Deployment Procedure

1. API Credential Generation

• Log into your designated Webflow management console.
• Navigate to the Site Settings area, then locate the Apps & Integrations section.
• Initiate the creation of a new API token.
• Securely copy the generated token value, as it will not be displayed again.

Alternatively, authentication via an OAuth Access Token is also supported.

2. Initial Repository Setup

Execute the necessary package installations:

bash npm install

3. Configuration of Runtime Environment Variables

For local testing and initial configuration, define these settings in a .env file (ensure this file is excluded from version control):

plaintext WEBFLOW_API_TOKEN=your-api-token-here

4. Claude Desktop Configuration Update

Modify your Claude Desktop configuration file to register this service:

On macOS:

bash code ~/Library/Application\ Support/Claude/claude_desktop_config.json

On Windows (using Command Prompt):

powershell code %AppData%\Claude\claude_desktop_config.json

Integrate or update the service definition within the JSON structure:

{ "mcpServers": { "webflow": { "command": "node", "args": [ "/ABSOLUTE/PATH/TO/YOUR/build/index.js" ], "env": { "WEBFLOW_API_TOKEN": "your-api-token" } } } }

Apply the changes by relaunching the Claude Desktop application.

Installation via Smithery

Automated installation for Claude Desktop users is achievable using the Smithery command-line utility:

bash npx -y @smithery/cli install @kapilduraphe/webflow-mcp-server --client claude

Exposed Capabilities (Tools)

The server presently exposes the following functional endpoints:

get_sites

Fetches a comprehensive catalog of all Webflow workspaces accessible by the authenticated credentials. The returned payload encompasses granular details, including:

• Human-readable Site Name and System Short Name
• Unique Site Identifier (ID) and Workspace Identifier (WorkspaceID)
• Chronological markers for creation, last modification, and final publication timestamps
• The designated Preview URL
• Time Zone configuration
• Settings related to assigned Custom Domains
• Localization structure (primary and secondary language configurations)
• Status of data collection features

get_site

Retrieves the complete attribute set for a singular Webflow site, identified by its siteId. This function yields an output structure identical to that of get_sites, but scoped to one entity.

Data Schema Definitions

typescript interface WebflowApiError { status?: number; message: string; code?: string; }

interface WebflowCustomDomain { id: string; url: string; lastPublished: string; }

interface WebflowLocale { id: string; cmsLocaleId: string; enabled: boolean; displayName: string; redirect: boolean; subdirectory: string; tag: string; }

interface WebflowSite { id: string; workspaceId: string; createdOn: string; displayName: string; shortName: string; lastPublished: string; lastUpdated: string; previewUrl: string; timeZone: string; parentFolderId?: string; customDomains: WebflowCustomDomain[]; locales: { primary: WebflowLocale; secondary: WebflowLocale[]; }; dataCollectionEnabled: boolean; dataCollectionType: string; }

Error Management Strategy

The service implements logic to gracefully manage several distinct failure modes:

Runtime Environment Faults

• Absence of the required WEBFLOW_API_TOKEN variable.
• Detection of an invalidated or incorrect API credential.

Diagnostic and Recovery Guide

Frequent Operational Hiccups

Tool Visibility Issues in Claude

• Review the console output logs generated by Claude Desktop.
• Confirm that WEBFLOW_API_TOKEN is correctly populated.
• Validate that the file path pointing to index.js is absolute and accurate.

Authorization Failures

• Reconfirm the validity and currency of your API credential.
• Inspect the permissions scope associated with the token.
• Check for any expiration dates on the credential.

Log Examination

To monitor the server's operational output:

On MacOS/Linux systems:

bash tail -n 20 -f ~/Library/Logs/Claude/mcp*.log

On Windows systems (PowerShell):

powershell Get-Content -Path "$env:AppData\Claude\Logs\mcp*.log" -Wait -Tail 20

Environment Variable Verification

If environmental variable errors persist, specifically confirm:

• WEBFLOW_API_TOKEN: Must contain a currently active and correctly formatted credential.

Security Posture

• Safeguard your API authentication key rigorously.
• Strictly avoid embedding sensitive credentials within source code repositories.
• Utilize environment variables exclusively for secret data injection.
• Institute a policy of periodic API token rotation.
• Actively monitor all API usage patterns originating from this token.
• Adhere to the principle of least privilege when setting token permissions.

Assistance Channels

Should difficulties arise:

• Consult the preceding Troubleshooting section.
• Scrutinize the logs emitted by Claude Desktop.
• Review any error reporting generated by the service process.
• Reference the official Webflow API documentation for endpoint specifics.

Licensing Information

This module is distributed under the terms of the MIT License. Full details are available in the accompanying LICENSE file.

WIKIPEDIA: Cloud computing is "a paradigm for enabling network access to a scalable and elastic pool of shareable physical or virtual resources with self-service provisioning and administration on-demand," according to ISO. It is commonly referred to as "the cloud".

== Key Attributes == In 2011, the National Institute of Standards and Technology (NIST) delineated five "essential characteristics" that define cloud systems. The precise NIST definitions are as follows:

On-demand self-service: "A consumer can unilaterally provision computing capabilities, such as server time and network storage, as needed automatically without requiring human interaction with each service provider." Broad network access: "Capabilities are available over the network and accessed through standard mechanisms that promote use by heterogeneous thin or thick client platforms (e.g., mobile phones, tablets, laptops, and workstations)." Resource pooling: " The provider's computing resources are pooled to serve multiple consumers using a multi-tenant model, with different physical and virtual resources dynamically assigned and reassigned according to consumer demand." Rapid elasticity: "Capabilities can be elastically provisioned and released, in some cases automatically, to scale rapidly outward and inward commensurate with demand. To the consumer, the capabilities available for provisioning often appear unlimited and can be appropriated in any quantity at any time." Measured service: "Cloud systems automatically control and optimize resource use by leveraging a metering capability at some level of abstraction appropriate to the type of service (e.g., storage, processing, bandwidth, and active user accounts). Resource usage can be monitored, controlled, and reported, providing transparency for both the provider and consumer of the utilized service. By 2023, the International Organization for Standardization (ISO) had expanded and refined the list.

== Historical Evolution ==

The conceptual lineage of distributed computing services dates back to the 1960s, marked by the rise of time-sharing concepts popularized through remote job entry (RJE). The prevailing operational model involved a "data center" structure, where end-users submitted batch jobs to specialized operators who executed them on large mainframe systems. This era was characterized by intense research and development aimed at maximizing the utility of expensive computational assets for a broader user base through optimized sharing of infrastructure, platform layers, and application execution, thereby boosting overall systemic throughput. The 'cloud' nomenclature for services leveraging virtualization emerged in 1994, initially employed by General Magic to describe the conceptual expanse of network locations reachable by their mobile software agents within the Telescript framework. This metaphor's adoption is attributed to David Hoffman, an internal communications strategist at General Magic, drawing from its prior established usage in telecommunications networking contexts. The term 'cloud computing' gained significant mainstream traction in 1996 following Compaq Computer Corporation's internal strategic planning document concerning future internet-based computation, signaling the firm's intent to transition towards widespread cloud infrastructure delivery.