# Webflow Alternative MCP > Webflow Alternative lets you manage entire web projects, CMS collections, pages, and assets directly through your AI client. Don't open the Designer; use this MCP to list sites, create new blog posts, update page SEO titles, or even trigger a full site publish cycle with natural language prompts. It gives developers and content teams programmatic control over every aspect of their Webflow build. ## Overview - **Category:** developer-tools - **Price:** Free - **Tags:** web-design, cms, no-code, site-management, api-automation ## Description Need to manage a set of web properties without logging into the dashboard? This MCP connects your AI agent directly to the Webflow Data API v2, giving you granular control over your site structure and content. You can list all accessible sites to check status or gather metadata. Need to update 50 blog posts' titles and descriptions across multiple collections? Your agent handles that bulk workflow. It lets you create new CMS items, manage media assets—uploading images or deleting old ones—and even set up webhooks for real-time event triggers. If you’re already using Vinkius as your central catalog, adding this Webflow connection means all your design and content tasks are run from one place. It's about treating the entire site like a database: listing pages, retrieving collection details, updating specific fields on items, or publishing the whole thing when it’s ready. No GUI required. ## Tools ### list_assets Retrieves a list of media files uploaded to a specific Webflow site. ### list_collections Lists all structured content collections available on the site. ### create_items Generates new pieces of content (items) within a specified CMS collection. ### create_webhook Sets up a real-time event notification trigger for the site. ### delete_asset Removes an existing media file from the site's asset library. ### delete_items Bulk removes content items from a specified CMS collection. ### list_forms Shows all contact or submission forms configured for the site. ### get_collection Fetches detailed structure and information about a specific CMS collection. ### get_form Retrieves the data schema for a particular site form. ### get_page Gets all metadata and structural details for a single web page. ### get_site Retrieves comprehensive details about an entire Webflow site. ### list_items Lists all existing content items within a defined CMS collection. ### list_pages Retrieves a list of every page that exists on the site. ### publish_site Triggers and executes the publication process for the entire Webflow site. ### list_sites Lists every single web project accessible under your account. ### update_items Modifies specific data points for existing content items in a CMS collection. ### update_page Changes the metadata, like SEO title or description, on a specific web page. ### upload_asset Adds new media files to the site's asset library. ### list_webhooks Lists all configured real-time event triggers on the site. ## Prompt Examples **Prompt:** ``` List all my Webflow sites and their IDs. ``` **Response:** ``` I've retrieved your sites. You have access to: 'Portfolio 2024' (ID: site_abc123) and 'Company Blog' (ID: site_xyz789). ``` **Prompt:** ``` Show me the items in the 'Blog Posts' collection with ID 507f1f77bcf86cd799439011. ``` **Response:** ``` Fetching items... I found 3 items in that collection: 'How to use MCP', 'Webflow Tips', and 'AI Automation Guide'. Would you like the details for any of these? ``` **Prompt:** ``` Publish the site with ID site_abc123. ``` **Response:** ``` Initiating publish for 'Portfolio 2024' (site_abc123)... The site has been successfully queued for publishing to its configured domains. ``` ## Capabilities ### Site Discovery and Status Check List all Webflow sites associated with your account to check their metadata and current status. ### Content Management System (CMS) Control Programmatically list, create, update, or delete entire content collections and individual items within them. ### Page Metadata Updates Retrieve details for specific web pages and modify their SEO titles and descriptions without touching the Designer tool. ### Asset Library Management List, upload, or delete media files (images, videos) from your site's central asset library. ### Site Publishing and Deployment Trigger the publishing process for an entire Webflow site to its live domains when content is finalized. ### Webhooks and Forms Access View form submissions or set up real-time event triggers using webhooks on your sites. ## Use Cases ### Migrating Content Before Launch A developer needs to ensure 30 new product pages are live before launch. They tell their agent, 'Use `list_collections` to check the Product collection schema, then use `create_items` for all pending products.' This bypasses manual entry entirely. ### Urgent SEO Fix Across Many Sites An SEO specialist realizes 15 important service pages are missing keywords in their titles. They instruct the agent to iterate through `list_pages`, then use `update_page` on each one with the correct metadata, solving a massive manual headache. ### Checking Site Health After Deployment The ops engineer wants to know which sites are ready for launch. They call `list_sites`, review the metadata provided by `get_site` on key projects, and only run `publish_site` when all green lights are confirmed. ### Building a Webhook Listener The team needs to know instantly when a contact form gets filled out. Instead of relying on manual checks, they use the agent to call `list_forms`, then execute `create_webhook` to set up automatic data routing. ## Benefits - Update CMS items or page metadata directly from your terminal. Instead of navigating through the Webflow designer, you can tell your agent to update 50 product descriptions using `update_items` or `update_page`. - Automate deployment steps. Use `list_sites` first to confirm all target sites are online, then trigger a full publish cycle with `publish_site`, saving the manual process of checking status across multiple dashboards. - Scale content creation effortlessly. If you have dozens of blog posts, your agent can use `create_items` in conjunction with provided data feeds, eliminating tedious copy-pasting into Webflow forms. - Control site assets like a database. You don't need to manually upload images; the `upload_asset` tool lets you manage media files programmatically and then reference them for content creation. - Audit your entire setup at once. Combine `list_pages` with `get_page` to quickly check every page's current SEO title, making a site-wide audit that used to take hours of clicking. ## How It Works The bottom line is that you run complex web management tasks through natural conversation, getting structured data and confirmations in return. 1. First, subscribe to this MCP and provide your Webflow API Token (v2). 2. Next, reference the site or content you want to modify within your AI client prompt. 3. Your agent executes the specific action—like creating items or updating page metadata—and reports success or failure back to you. ## Frequently Asked Questions **How do I update SEO titles using Webflow Alternative MCP?** You use the `update_page` tool to modify metadata. You simply provide the page ID and the new title or description in your prompt, letting your agent make the API call. **Does Webflow Alternative MCP handle publishing sites?** Yes, it uses the `publish_site` tool to initiate deployment. Just be mindful that there's a rate limit of one successful publish per minute. **What if I want to add a new image? Should I use upload_asset?** Yep, you need `upload_asset`. This tool adds the file to the site’s central media library. After uploading, you'll get an asset ID that you can then reference when creating content. **Can I delete multiple blog posts at once?** You use `delete_items` for this. First, you might call `list_collections` to confirm the right collection, and then specify which item IDs need removal in your prompt. **How can I check if my site has any forms?** You run `list_forms`. This shows all the submission points on the site. You can then use `get_form` to see what fields are expected for each one.