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 VS Code Copilot 10 tools — connect in under 2 minutes

Name: Webflow
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Webflow and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "webflow": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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.

GitHub Copilot Agent mode brings Webflow data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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 VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Webflow MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Webflow

Ask Copilot: "Using Webflow, help me...". 10 tools available

Why Use VS Code Copilot with the Webflow MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Webflow through the Model Context Protocol.

VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Webflow + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Webflow MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Webflow MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Webflow to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Webflow to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Webflow + VS Code Copilot FAQ

Common questions about integrating Webflow MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.