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 aft

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.

Webflow MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Webflow
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Webflow through the Vinkius — pass the Edge URL in the `mcps` parameter and every Webflow tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Webflow Specialist",
    goal="Help users interact with Webflow effectively",
    backstory=(
        "You are an expert at leveraging Webflow tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Webflow "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Webflow MCP Server

Connect Webflow to your AI agent and manage your websites, CMS content, and e-commerce data conversationally.

When paired with CrewAI, Webflow becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Webflow tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

CMS Management — List, create, update, and delete CMS collection items (blog posts, portfolio entries, product listings) from natural language.
Site Publishing — Trigger site publishes and check publish status across staging and production domains.
Collection Schema — Query collection structures, field types, and validation rules to understand your content model.
E-commerce Data — Retrieve orders, products, and inventory data from Webflow's built-in e-commerce engine.

The Webflow MCP Server exposes 10 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Webflow to CrewAI via MCP

Follow these steps to integrate the Webflow MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 10 tools from Webflow

Why Use CrewAI with the Webflow MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Webflow through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Webflow + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Webflow MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Webflow for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Webflow, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Webflow tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Webflow against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Webflow MCP Tools for CrewAI (10)

These 10 tools become available when you connect Webflow to CrewAI via MCP:

create_collection_item

Create a CMS item

get_site

Get site details

get_user

Get authorized user info

list_collection_items

List items in a collection

list_collections

List CMS collections

list_domains

List site domains

list_pages

List all site pages

list_sites

List all Webflow sites

publish_site

Publish site to production

update_collection_item

Update a CMS item

Example Prompts for Webflow in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Webflow immediately.

"List all blog posts in my Webflow CMS."

"Publish my Webflow site to production."

"Create a new blog post titled 'How AI Transforms Marketing'."

Troubleshooting Webflow MCP Server with CrewAI

Common issues when connecting Webflow to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Webflow + CrewAI FAQ

Common questions about integrating Webflow MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.