Connecting an agent to Webflow is not only a setup step. It also defines where the agent can work, what it can access, and which permissions apply when it starts using Webflow tools.

That is worth understanding before you ask it to do real work on your site.

Getting connected

If you're using Claude, you’ll start by adding the Webflow connector. Then, sign in to Webflow through the authorization window, choose a workspace, and authorize the connection.

Once connected, the Webflow connector appears as active in Claude, and the agent can use Webflow MCP tools within the workspace you selected.

To add connectors in Claude, you'll need a Claude account with connector support. Check your plan if you're not sure whether connectors are available to you.

What about Claude Code?

Claude Code is a developer-focused version of Claude that runs from a terminal or code editor. It can also connect to the Webflow MCP server, so many of the same Webflow tasks are possible.

The connection works differently. Claude Chat connects through the Connectors menu and Webflow's authorization flow. Claude Code connects through MCP configuration in your terminal or editor.

What you authorized

No matter which agent you use, when you authorize MCP, you choose where the agent can work. Depending on the authorization flow, that may mean authorizing a full Webflow workspace or selecting a specific site within that workspace.

After you connect, you may also be able to customize how your agent works with Webflow MCP tools.

Two boundaries especially matter:

• Workspace and site scope. If your team has one workspace for client sites and another for internal projects, authorizing the client workspace does not give the agent access to the internal projects workspace. If you authorize a single site, the agent works within that site rather than across every site in the workspace.
• Role permissions. The Webflow MCP server follows your existing Webflow permissions. If your role lets you edit CMS content, the agent can help with CMS tasks. If your role does not let you edit components or styles, the agent cannot use MCP to do that for you.

Only Webflow site owners and admins can authorize the MCP server. If you do not have that level of access, ask a site owner or admin to complete the authorization before you begin.

Before your first prompt

A few setup choices make your first MCP session easier to manage.

• Use a safe site. Work on a test site, cloned site, or non-production site while you're learning.
• Create a backup. This is good practice before any session that could change site structure, styles, CMS content, or page settings.
• Start with a small task. Ask the agent to list pages, check metadata, or inspect CMS structure before asking it to make broader changes.

Once you're connected, the next step is not asking the agent to do everything at once. It's writing a prompt with enough context, direction, and boundaries for the agent to work well.

Ready to continue?

Click Complete & continue to learn how to write a prompt that gives your agent the context and constraints it needs before it acts.