Overview

The Webflow MCP Server provides a lightweight bridge between external tooling and Webflow projects. It exposes a set of REST endpoints and adapters that make it straightforward to inspect sites, enumerate pages and CMS collections, and perform programmatic updates. The server is intended for developers who need to automate common content operations (bulk updates, syncs, templated page creation) without embedding Webflow API calls directly in every script or CI job.

By centralizing Webflow interactions behind a small local service, teams can build automations, integrate with CI/CD pipelines, or connect other systems (headless CMS, e-commerce platforms, translation services) in a reproducible way. The MCP server is useful for local development, scheduled sync jobs, and as a stable interface for interacting with Webflow resources across projects.

Features

Expose site, page, and collection metadata via simple REST endpoints
Read and write CMS collection items (create, update, publish)
Enumerate pages and templates for a given Webflow site
Support for bulk operations to minimize API call overhead
Simple configuration through environment variables and a .env file
Local development mode with verbose logging for debugging automation flows

Installation / Configuration

Prerequisites:

Node.js (LTS recommended)
A Webflow API token (generate from your Webflow account)

Clone, install, and run:

git clone https://github.com/webflow/mcp-server.git
cd mcp-server
npm install
npm run start

Typical environment configuration (.env):

# Webflow API token with the scope required for sites and CMS
WEBFLOW_API_TOKEN=your_webflow_api_token_here

# Optional: port to run the server on
PORT=3000

# Optional: log level (debug, info, warn, error)
LOG_LEVEL=info

Run in development (with nodemon, if included):

npm run dev

You can also containerize the server. Example Dockerfile usage:

docker build -t webflow-mcp-server .
docker run -e WEBFLOW_API_TOKEN=$WEBFLOW_API_TOKEN -p 3000:3000 webflow-mcp-server

Available Resources

The server exposes a small set of HTTP endpoints to interact with Webflow resources. The exact routes may vary by release; the examples below show the types of operations commonly provided.

Endpoint	Method	Description
/sites	GET	List all accessible Webflow sites
/sites/:siteId/pages	GET	List pages for a site
/sites/:siteId/collections	GET	List CMS collections for a site
/collections/:collectionId/items	GET	List items in a CMS collection
/collections/:collectionId/items	POST	Create a new CMS item
/collections/:collectionId/items/:itemId	PUT	Update a CMS item
/collections/:collectionId/items/:itemId/publish	POST	(Optional) Publish an item or trigger site publish

Note: Check the repository README or open the server code to confirm the exact route names and supported parameters.

Sample curl requests

List sites:

curl -H "Authorization: Bearer $WEBFLOW_API_TOKEN" http://localhost:3000/sites

Get collection items:

curl -H "Authorization: Bearer $WEBFLOW_API_TOKEN" \
  http://localhost:3000/collections/<COLLECTION_ID>/items

Create a new collection item (example payload):

curl -X POST -H "Content-Type: application/json" \
  -H "Authorization: Bearer $WEBFLOW_API_TOKEN" \
  -d '{
    "fields": {
      "name": "New Item Title",
      "slug": "new-item-title",
      "body": "<p>Item body content</p>"
    },
    "publish": true
  }' \
  http://localhost:3000/collections/<COLLECTION_ID>/items

Use Cases

Bulk content updates: Update fields across hundreds of CMS items in a single job. Use the server to page through collection items and apply consistent transformations (e.g., update image asset URLs, normalize tags).
Content sync / migrations: Move content from a headless CMS, spreadsheet, or external database into Webflow. The MCP server can act as the synchronization target for incremental imports and reconciliations.
Automated publish flows: Trigger item creation or updates and then publish the site (or individual items) as part of a CI/CD pipeline after content or template changes.
Localization and multi-site management: Push translated copies of collection items or pages to multiple Webflow sites, using the server to coordinate repeated tasks and ensure consistent field mappings.
Template-driven page generation: Generate pages based on templates and populate CMS collections programmatically for marketing campaigns or seasonal landing pages.

Tips for Developers

Use environment variables to separate credentials across environments (development, staging, production).
Implement retry/backoff logic in clients that call the MCP server for large batch jobs to handle transient errors gracefully.
When performing mass updates, test on a small subset first and confirm the expected changes in a staging site.
Refer to the Webflow API documentation alongside the MCP server code if you need to implement custom endpoints or extend server behavior.

Repository and source code: https://github.com/webflow/mcp-server

For implementation details, available endpoints, and configuration options, inspect the repository’s code and README to match the exact shape of requests and supported parameters.

Webflow MCP Server: Interact with Sites, Pages, Collections