Webflow Operational Gateway (MCP)

This specialized Message Control Protocol (MCP) server acts as the conduit allowing Claude to execute operations against the official Webflow RESTful APIs.

Prerequisites for Deployment

• Runtime environment: Node.js (version 16 or newer required)
• Client software: Claude Desktop Application
• Service entitlement: Active Webflow Account
• Authorization credential: Valid Webflow API Token (either a specific Site token or an OAuth 2.0 Access Token)

Configuration & Deployment Steps

Step 1: Token Generation

1. Authenticate within your primary Webflow console.
2. Navigate to the settings panel for the target site, specifically the 'Apps & Integrations' section.
3. Initiate the creation of a new API credential.
4. Securely record the generated token value, as this credential will not be displayed again.

Alternatively, integration via an OAuth Access Token is supported.

Step 2: Project Initialization

Execute dependency installation within the project directory:

bash npm install

Step 3: Environment Variable Setup

Establish a local configuration file named .env (ensure it is excluded from version control):

plaintext WEBFLOW_API_TOKEN=your-specific-api-token-here

Step 4: Claude Desktop Integration

Modify the Claude Desktop configuration file. The path varies by operating system:

MacOS Path:

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

Windows Path:

bash code %AppData%\Claude\claude_desktop_config.json

Inject or update the server configuration object as follows, substituting /ABSOLUTE/PATH/TO/YOUR/build/index.js with the actual executable location and utilizing the token:

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

Save the configuration and relaunch the Claude Desktop client to recognize the new service endpoint.

Automated Installation via Smithery

For streamlined deployment, utilize the Smithery CLI to register this server:

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

Exposed Functionality (Tools)

This interface currently exposes the following actionable functions:

get_sites

Fetches a comprehensive manifest of every Webflow site associated with the authenticated credential. The returned data set includes comprehensive metadata such as:

• Human-readable Site Name and Canonical Short Name
• Unique Identifiers (Site ID and Workspace ID)
• Timestamps for site creation, last modification, and last publication event
• The site's designated Preview URL
• Time Zone configuration details
• Status and configuration of associated Custom Domains
• Localization definitions (primary and secondary language setups)
• Settings pertaining to Content Collection enablement

get_site

Queries and returns the full, granular details for a single, specified Webflow property, identified via its unique siteId. The output structure mirrors that provided by the get_sites operation, but scoped to one entity.

get_collections

Retrieves an inventory of all Content Collections residing within a designated Webflow site (requires siteId). For each collection, metadata is provided, including:

• Internal ID (_id) and Human-readable Name
• Record of creation and last modification
• The collection's designated URL slug
• Singular nomenclature if applicable
• The current count of items within the collection
• Structural Collection Settings and schema definitions

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; }

interface WebflowCollection { _id: string; lastUpdated: string; createdOn: string; name: string; slug: string; singularName: string; itemCount: number; }

interface WebflowCollectionsResponse { collections: WebflowCollection[]; }

Operational Error Management

The server implements routines to trap and report common operational failures:

Configuration Errors (Environment)

• Absence of the required WEBFLOW_API_TOKEN environment variable.
• Detection of an invalid or improperly formatted API key.

Debugging and Resolution

Non-Appearing Tools in Claude Interface

• Consult the latest entries in the Claude Desktop system logs for runtime exceptions.
• Confirm the presence and correctness of the WEBFLOW_API_TOKEN value.
• Verify that the specified path to the executable (index.js) is absolute and correctly resolved.

Authentication Failures

• Revalidate the API key's accuracy and its active status.
• Inspect the token's assigned permission scope to ensure required API access levels are granted.
• Confirm the credential has not reached its expiration date.

Accessing Server Transaction Logs

To monitor ongoing server activity and diagnostics:

MacOS/Linux Streams:

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

Windows PowerShell Stream:

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

Environment Variable Sanity Check

If diagnostics point toward environment issues, confirm:

• WEBFLOW_API_TOKEN: Must correspond to a functional, non-revoked credential.

Security Protocols

• Exercise extreme caution to safeguard the confidentiality of the API access key.
• Strictly prohibit the commitment of any secret credentials into source control repositories.
• Prioritize the use of runtime environment variables over hardcoding sensitive parameters.
• Implement a regular schedule for API token rotation/renewal.
• Rigorously track and audit API consumption patterns within the Webflow dashboard.
• Adhere to the principle of least privilege when defining token capabilities.

Support Channel

Should issues persist after consulting the diagnostics guide:

• Revisit the troubleshooting steps outlined above.
• Review detailed outputs from the Claude Desktop logs.
• Analyze the diagnostic data outputted directly by the server process.
• Consult the authoritative Webflow API documentation for external reference.

Licensing

This component is released under the MIT License. Full details are available in the LICENSE file.

WIKIPEDIA: Cloud computing, often termed 'the cloud,' is defined by ISO as "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."

== Defining Attributes == In 2011, the National Institute of Standards and Technology (NIST) established five fundamental criteria characterizing cloud environments. These are the official NIST definitions:

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 updated and enhanced this foundational list.

== Historical Context ==

The conceptual foundation for cloud infrastructure traces back to the 1960s with the rise of time-sharing systems and Remote Job Entry (RJE). In that era, centralized mainframe operations required users to submit tasks to dedicated operators. This period was defined by efforts to maximize the utility of costly computing assets through shared access models, optimizing underlying hardware, platform abstractions, and application delivery for end-users. The specific graphic representation of 'the cloud' for networked services originated around 1994, employed by General Magic to delineate the conceptual 'space' for mobile agents within their Telescript framework. This visual shorthand is commonly attributed to David Hoffman, a communications professional at General Magic, drawing from established conventions in telecommunications networking. The term 'cloud computing' gained widespread recognition in 1996 when Compaq Computer Corporation detailed a strategic business blueprint focusing on future internet infrastructure.