Beta server

To connect to the Beta MCP server, connect manually with the server URL https://mcp.webflow.com/beta/mcp.

The Webflow Claude connector and Grok Build plugin connect to the production MCP server, so to connect to the Beta MCP server, configure each client manually with the beta URL.

Claude Code

Install Claude Code CLI

If you haven’t installed Claude Code yet, follow the installation guide.

Verify the installation:

claude --version

Add the Webflow Beta MCP server

Use the CLI to add the Webflow Beta MCP server:

claude mcp add --transport http webflow-beta https://mcp.webflow.com/beta/mcp

This command adds the Webflow Beta MCP server to your Claude Code configuration.

Authorize the MCP server and app

Start Claude Code:

claude

When Claude Code is running, use the /mcp command to manage MCP servers:

/mcp list

Select the Webflow Beta MCP server from the list. If you haven’t authenticated yet, Claude Code automatically opens a browser window that shows an OAuth login page where you can authorize the Webflow sites you want the MCP server to access and install the MCP Bridge App.

Write your first prompt

Start interacting with the MCP server in your AI agent’s chat window. Try prompts like:

List all my collections and show me their field structures

Audit my site for broken links, missing alt text, and incomplete meta descriptions

Create a responsive hero section with a headline, description, and CTA button

Claude Desktop

To connect Claude Desktop to the Beta MCP server, use the instructions in Connecting Claude Desktop manually with the URL of the Beta MCP server: https://mcp.webflow.com/beta/mcp.

Grok Build

Add the Beta MCP server to Grok Build

In the left sidebar, click Customize and select the MCPs filter.
Click New MCP Server (Add a Custom MCP Server). Grok Build opens mcp.json.
Paste the following configuration into .cursor/mcp.json (or add the webflow-beta entry to your existing configuration):
.cursor/mcp.json
```
{
  "mcpServers": {
    "webflow-beta": {
      "url": "https://mcp.webflow.com/beta/mcp"
    }
  }
}
```
Use project-specific MCP configuration to avoid repeated auth prompts
Configure mcp.json per project instead of using Grok Build’s global settings. This configuration prevents repeated authentication prompts when opening multiple Grok Build windows without being authenticated.
Save and close the file.

Authorize the MCP server and app

In the left sidebar, click Customize and select the MCPs filter.
Next to the Webflow MCP server, click Authenticate.
Grok Build automatically opens an OAuth login page where you authorize the Webflow sites you want to access and install the MCP Bridge App.
When authorization is complete, the Webflow MCP indicator turns green.

Limit authorized sites

Limit the number of sites for security and performance. To reauthorize, open the Webflow Beta MCP server in Customize → MCPs and click Logout under Environments.

Write your first prompt

Start interacting with the MCP server in your AI agent’s chat window. Try prompts like:

List all my collections and show me their field structures

Audit my site for broken links, missing alt text, and incomplete meta descriptions

Create a responsive hero section with a headline, description, and CTA button