Webflow MCP. Manage Content and Publish Sites Conversationally
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Webflow MCP Server gives your AI agent direct API access to manage Webflow sites and content. You can list collections, create new CMS items (like blog posts or product listings), update existing data, check site analytics, and trigger full production publishes—all without opening the Webflow Designer.
What your AI agents can do
Create collection item
Creates a new content item within a specified CMS collection.
Get site
Retrieves key details about the specific Webflow site being managed.
Get user
Gets information about the currently authorized user for permission checks.
Use tools like create_collection_item and update_collection_item to programmatically manage all content within your defined collections.
Execute the publish_site tool to push changes live, checking status across multiple domains like staging and production.
Query site details using list_collections, list_pages, or get_site to understand the full scope of content available on a given Webflow build.
Access specific data points like orders and product inventory using dedicated tools, keeping your AI agent connected to transactional business logic.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Webflow MCP Server: 10 Tools for Site and Content Management
These tools let your AI agent interact with every major part of your Webflow site—from publishing to managing product listings.
019d7621create collection item
Creates a new content item within a specified CMS collection.
019d7621get site
Retrieves key details about the specific Webflow site being managed.
019d7621get user
Gets information about the currently authorized user for permission checks.
019d7621list collection items
Lists all existing content items inside a specified CMS collection.
019d7621list collections
Retrieves a list of all available CMS collections on the site.
019d7621list domains
Shows all domains associated with the Webflow account.
019d7621list pages
Lists every page currently built into the website structure.
019d7621list sites
Retrieves a list of all Webflow sites available under the connected account.
019d7621publish site
Triggers the live publishing process, making changes visible to the public.
019d7621update collection item
Modifies an existing content item within a CMS collection.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Webflow, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
Look, you need your AI agent talking directly to Webflow's API for this thing to work. This server gives your agent full control over managing sites and CMS content without you ever having to open the actual Designer. You can run commands like listing everything or updating records just by telling your agent what to do.
Discovering Your Site Structure
You gotta know what's even there before you mess with it. Use list_sites to get a list of every Webflow account site connected under the main credential. Once that’s sorted, get_site pulls key details for the specific build you’re working on. You can run list_collections to see all the content buckets available—the entire schema, basically.
Then, if you want to scope out what pages are live, list_pages gives you every page built into that structure. It's also got list_domains, so your agent knows exactly which domains are associated with the account.
Managing CMS Content
The whole point is often the content, right? The server lets you talk to any defined collection using tools like list_collection_items. This shows everything that’s already sitting in a specific CMS bucket—all your existing blog posts or product listings. If you need to drop new content, run create_collection_item and it handles making the item live in that specified collection.
And if something needs tweaking, update_collection_item lets you modify any piece of data without starting from scratch. These tools cover everything—from listing all items to building out an entirely new record.
Deployment and Publishing
Changing content is one thing; getting it public is another. You use the publish_site tool when you're ready to push changes live, making sure your work shows up on the web. This handles status checks across different environments, like staging or production. For context or permission checking, your agent can check who’s logged in using get_user, giving it the necessary credentials to execute tasks correctly.
It's a complete loop: You discover the site structure with list_collections and list_pages. You populate the content by creating or updating items via create_collection_item or update_collection_item. Then, when you’re ready for folks to see it, you trigger the full push using publish_site. You don't need any other tools in this stack.
It handles all of it.
How Webflow MCP Works
- 1 Subscribe to the Webflow integration on the marketplace. Then, generate an API token within your Webflow site's settings (Site Settings → Apps & integrations).
- 2 Pass that generated API token and necessary credentials to your AI client/agent.
- 3 Ask your agent to execute a task—for instance, 'List all blog posts in my main collection,' or 'Publish the staging site to production.' The agent handles the rest.
The bottom line is you hand off the complex API calls and manual webflow navigation to your AI client; it talks to Webflow using the tools you expose.
Who Is Webflow MCP For?
This is for content ops teams, agency account managers, and e-commerce specialists who are constantly fighting developer bottlenecks. If your job involves moving content from Draft status to Live production—or managing multiple client sites simultaneously—you need this. It puts Webflow's backend controls directly into the chat window.
Needs to create and modify hundreds of blog posts or portfolio entries quickly. They use create_collection_item and update_collection_item instead of logging into the CMS editor.
Manages several client sites concurrently. They use list_sites and publish_site to trigger bulk deployments across multiple accounts from one dashboard.
Needs real-time data on inventory or recent orders. They ask the agent to query product details, bypassing manual database checks.
What Changes When You Connect
- Speed up your content workflow. Instead of logging into the CMS editor to add 50 blog posts, ask the agent to run
create_collection_itemrepeatedly for all required drafts. - Gain full visibility across client accounts. Use
list_sitesand then target specific domains withpublish_site, letting you manage multiple web properties without switching tabs or logins. - Avoid developer dependency on publishing. You can trigger a production deploy instantly by asking the agent to run
publish_site, checking status immediately afterward. - Understand your data structure before writing anything. Use
list_collectionsandlist_pagesfirst to map out exactly which content types and pages exist, preventing wasted API calls. - Maintain data integrity by working directly with records. If you need to change a product description or portfolio detail, use
update_collection_iteminstead of manually editing the page.
Real-World Use Cases
Bulk Content Update for a Client Campaign
A marketing team needs to update 40 old case study pages with new client data. Instead of downloading an Excel sheet and logging in 40 times, they tell the agent: 'Use list_collections to find 'Case Studies,' then use update_collection_item for the specific records.' The agent handles the loop, saving hours.
Pre-Launch Site Testing
A developer finishes a new section and needs to check if it publishes correctly before hitting the main site. They ask the agent to run get_site for the staging domain, then trigger a limited publish using publish_site, confirming the live status right in the chat.
Auditing Site Structure
An operations manager joins a new client account and needs to know what content types exist. They ask the agent, 'What collections do we have?' The agent runs list_collections, providing an immediate inventory of all possible data sources.
Emergency Content Fix
A product listing accidentally went live with outdated pricing. Instead of navigating to the page and editing it, the content specialist tells the agent: 'Update the price for product ID 123.' The agent executes update_collection_item instantly.
The Tradeoffs
Assuming all data is accessible
Asking the agent to update a content item without first confirming its existence or structure. This leads to API errors and workflow failure.
→
Always start by running list_collections to see what collections are available, then use list_collection_items to confirm the specific record ID you need before calling update_collection_item.
Trying to publish without confirmation
Running a publishing command (publish_site) and assuming it worked. You have no idea if it failed, or which domains were actually updated.
→
After running publish_site, immediately ask the agent to check the site status using get_site to confirm the last publish time and successful domain rollout.
Manual data handling
Copying a blog post title from an email, opening Webflow, pasting it into the CMS editor, and manually setting the slug. This is slow and error-prone.
→
Use create_collection_item directly in your chat prompt, providing all required fields (title, body, slug) in one go. The agent builds the record for you.
When It Fits, When It Doesn't
You need this Webflow MCP Server if your workflow involves repetitive, multi-step actions across structured content or requires triggering specific platform events like publishing. Specifically: 1. If you manage CMS data (blog posts, products) and need to create/modify records in bulk, use create_collection_item and update_collection_item. 2. If your job involves client deployment cycles, the publish_site tool is non-negotiable. Don't use this if you only want to view content or read analytics; your AI client can usually handle that with basic web browsing tools. If your goal is simply to check what collections exist, running list_collections first saves time and prevents bad calls.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Webflow. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Updating a single blog post shouldn't require logging into the CMS editor.
Today, changing one product description means navigating to Webflow. You log in, find the project, click on the Collection page, locate the specific item ID, open the fields, paste your new text, and hit save. If you have five pages, that's ten minutes of clicks, scrolling, and potential context switching.
With this MCP server, you just talk to your agent. You say, 'Update product X with these details.' The agent uses `update_collection_item` under the hood—it bypasses all the UI clicks and gets straight to the data layer. You get the change confirmed in seconds.
Webflow MCP Server: Publish sites directly from your chat.
Manually publishing a site means logging into Webflow, navigating to the publish settings, and hitting that big button. If you're managing multiple staging environments for different clients, this process is repeated dozens of times across different browsers and dashboards.
Now, your agent handles it. You ask it to run `publish_site`. It triggers the full deployment sequence and confirms success right back in your chat interface. The manual button-clicking part is gone.
Common Questions About Webflow MCP
How do I get my Webflow API token? +
Log in to your Webflow Dashboard. Open the site you want to connect and click the gear icon to access Site Settings. In the left sidebar, click Apps & integrations. Scroll to the API access section at the bottom and click Generate API token. Name your token, select the required permission scopes (e.g., CMS read/write, Sites publish), and click Generate token. Copy it immediately — Webflow will not show the full token again. Each site can have up to 5 tokens. Tokens expire after 365 days of inactivity.
Can my AI agent publish a blog post to my Webflow site? +
Yes. Your AI agent can create CMS collection items (like blog posts), set all fields including title, body, slug, thumbnail, and publish date, then trigger a site publish — all in one conversation. Perfect for content teams who want to skip the Webflow designer and go from draft to live in seconds.
What if I manage multiple client sites as an agency? +
Each Webflow site has its own API token, so you can configure multiple integrations — one per client site. This lets your AI agent switch between projects, bulk-update CMS content across sites, or publish changes to specific client domains without mixing data between accounts.
Can I track e-commerce orders through my AI agent? +
Yes. If you use Webflow's built-in e-commerce, your AI agent can retrieve orders, order details, fulfillment statuses, and product inventory — giving you a real-time view of sales activity without opening the Webflow dashboard or exporting reports.
When I run `list_collections` or `create_collection_item`, how does the Webflow MCP Server handle content validation? +
The server validates your data against the defined schema. When you call tools like create_collection_item, it checks field types and required rules before submitting, preventing invalid records from being created.
If my site publish fails after using `publish_site`, how can I diagnose the issue with Webflow MCP? +
The server provides specific error codes and detailed logs when a publish action fails. Use the available status tools to pinpoint whether the failure is due to content, permissions, or network issues.
Are there rate limits if I frequently call `list_sites` for multiple client domains? +
Yes, all API interactions adhere to Webflow's standard rate limiting policies. We recommend batching your requests and monitoring the documentation for specific throttling thresholds.
When using `update_collection_item`, can I target only specific fields without overwriting the entire record? +
Absolutely. The tool supports partial updates, meaning you send data for the exact fields you want to change. This preserves existing content in other collection attributes.
Multi-server workflows that include Webflow MCP
Audit Agency Websites Using MCP Servers
Your agency manages 15 client Webflow sites but nobody checks if last month's landing page update actually improved conversions , the designer shipped it, the PM marked it done, and the page sits there with a 0.4% conversion rate that nobody measures
MCP Recipe for Content Distribution Automation
You publish a blog post in Webflow and then spend 45 minutes manually reformatting it for your newsletter, copying stats into a spreadsheet, and wondering why your best content never reaches your subscribers
MCP Recipe to Optimize Client Conversion Rates
Your agency redesigned the client's homepage 3 weeks ago and everybody celebrated , but nobody checked Mixpanel to see that the new hero section reduced signups by 22% because the CTA button blends into the background on mobile
MCP Workflow for CMS to Email Campaigns
New CMS content published, subscriber list segmented, email campaign sent , your agent runs content distribution
Publish Designs to Webflow Using MCP Servers
Your designer finishes the Figma mockup on Tuesday, the social media manager recreates it in Canva on Wednesday, and the web developer rebuilds it in Webflow on Thursday , three people doing versions of the same work for the same client
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Agility CMS
Manage and query your Agility CMS content through AI — navigate sitemaps, search lists, and fetch layouts.
Fourier Transform Engine
Calculate Fast Fourier Transforms (FFT) on time-series data local. Extract dominant frequencies from signals, audio, or financial cycles with mathematical perfection.
Geocode.xyz
Convert addresses to coordinates, perform reverse geocoding, and extract location data from text with Geocode.xyz.
You might also like
Offerslook
Manage performance marketing via Offerslook — track offers, advertisers, and affiliates directly from your AI agent.
SimpleHash (Multi-chain NFT API)
Access comprehensive NFT data across 50+ chains — query wallet holdings, metadata, collection details, and transfer history.
Crypto Random String
Generate cryptographically secure random strings for API keys, tokens, and invite codes using Node.js crypto.randomBytes().