SpritesWhat Sprites does on Webflow
Every door runs the Webflow specialist, which reads the account itself. You do not brief it on which account, campaign or page you mean.
Posts land in your CMS collection
The article is mapped onto your collection’s own fields — name, slug, the rich-text body and the meta fields when the collection has them — and created as a draft item, not pasted into the chat.
Page titles and meta, page by page
Page title, slug, SEO title, meta description and Open Graph title and description, each change shown with its before and after, and the length search results display noted beside it.
Copy edits that do not undo the Designer
A text change is built from the page as it reads now, in the same conversation. An edit drafted from an older copy would quietly revert work done in the Designer since, so Sprites refuses to send one.
Every write is checked after it lands
After an approved change applies, Sprites reads the record back from Webflow and compares it with what you approved, so “done” means the site now says it.
Search Console in the same conversation
Queries you rank 8–20 for, pages that slipped, and the post or metadata change that would close the gap — asked and answered without changing tools.
Going live is its own yes
CMS items are created as drafts. Publishing one is a separate action with its own approval card.
Official Webflow MCP vs open-source servers vs Sprites
Three ways to put Webflow behind Claude, ChatGPT or any other MCP client, and what each one can actually do.
Official Webflow MCP
Webflow hosts its own MCP server at mcp.webflow.com/mcp with OAuth sign-in. Its design tools work on layouts, elements, styles, components and interactions; its content tools reach CMS collections, pages, SEO fields, assets and forms.
Open-source servers
Webflow’s server is itself open source, as webflow/mcp-server on GitHub, so the self-hosted route runs Webflow’s own code against a site token you manage.
Sprites MCP
Sprites leaves design alone. It decides what to write from keyword research, Search Console and a read of your pages, then writes CMS items, SEO fields and copy edits as approval cards, each read back from Webflow after it applies.
The full comparison is further down: Webflow’s own server.
Webflow jobs to hand your agent
Start to finish, in any connected client: what you type, what Sprites does with it, and what comes back to approve.
The metadata sweep
YouWith Sprites, find every Webflow page with a missing or overlong meta description and fix them.
- Sprites does
- Lists your pages, checks titles and descriptions against search-result limits, and reads Search Console for what each page already ranks for.
- You get back
- One approval card per page, with the current and proposed fields side by side.
Post into the CMS
YouAsk Sprites to write a post on "webflow localization seo" and add it to our blog collection.
- Sprites does
- Researches the keyword, reads what ranks, writes the post and maps it onto your collection’s fields.
- You get back
- A draft CMS item. Publishing it is a separate approval.
Refresh a slipping page
YouUse Sprites to find the blog post that lost the most clicks this month and refresh it.
- Sprites does
- Compares Search Console periods, picks the post, re-reads it and the pages now outranking it.
- You get back
- An updated item with the changed fields shown before and after, ready to approve.
Connect Webflow to your agent
One endpoint, five clients. Each guide is the exact path through that host's settings, the URL to paste, and the first prompt to run.
Your AI agent
Your ad accounts
The only host that draws the Sprites approval card in the chat, so you edit a budget or a headline in place and approve it without leaving the thread.
Approval card in the threadWebflow MCP for ChatGPTDeveloper mode gives ChatGPT full read-and-write MCP tools rather than the search-and-fetch pair the built-in connectors are limited to, and the Apps SDK renders the Sprites card in the thread.
Approval card in the threadWebflow MCP for CodexMarketing work that belongs in a commit: Codex can read the landing page it is about to ship and brief Sprites on the campaign pointing at it, in one session.
Results as text · approve in SpritesWebflow MCP for CursorThe campaign and the page it points at live in the same window: change the pricing copy, then have Sprites update the ads that quote it, without a second tool.
Results as text · approve in SpritesWebflow MCP for GrokGrok reads the live timeline, so the same thread that spots a trend can brief the campaign that rides it.
Results as text · approve in SpritesWebflow MCP for GeminiThe account and the analytics are already Google: Gemini reads Google Ads and GA4 alongside Search Console without leaving the family it belongs to.
Results as text · approve in SpritesWebflow MCP for GitHub CopilotMarketing data inside the editor where the tracking code lives, so a conversion event can be checked against what GA4 actually recorded before the pull request is opened.
Results as text · approve in SpritesWebflow MCP for Google AntigravityOne MCP configuration shared by the IDE, the CLI, the SDK and Antigravity 2.0, so the connector is added once and every surface has it.
Results as text · approve in SpritesOfficial Webflow MCP vs Sprites MCP
Yes, there is an official one: Webflow runs its own MCP server at mcp.webflow.com/mcp. Here is what each covers.
Webflow publishes its own MCP server, open source and hosted at mcp.webflow.com/mcp with OAuth sign-in. Its design tools work on the site itself — layouts, elements, styles, components, interactions and custom code — and its content tools reach CMS collections and items, pages, SEO, assets, forms and the sitemap. A few canvas actions, such as reading the current selection or breakpoint, need the Designer open with the MCP Bridge App, which installs during sign-in. Each authorization covers one workspace.
| Webflow officialmcp.webflow.com/mcp | Sprites MCPapproval-gated | |
|---|---|---|
| Endpoint | mcp.webflow.com/mcp | mcp.sprites.ai/mcp |
| Setup | OAuth sign-in, one workspace per authorization | Site API token and Site ID pasted into Sprites once; the agent never holds them |
| The canvas | Layouts, elements, styles, components and interactions | Not touched — text on existing elements only |
| Deciding what to write | Writes what the model asks for | Keyword research, Search Console and a read of your pages first |
| Writes | Design and content, applied when the tool is called | An approval card with before and after, then read back from Webflow and verified |
| Copy edits | Whatever text the model sends | Built from the page as read in the same conversation, so Designer edits are not reverted |
| Other channels | Webflow | Webflow plus Search Console, GA4, Google Ads, Meta and more |
If you want an agent to build or restyle pages, Webflow’s own server is the right tool; Sprites does not touch design. Use Sprites when the job is search: what to write, which page to fix, and a change you can read before it lands on your site.
Why a connector like Sprites for Webflow ads
The agent is the interface; the connector decides what it can see and what it is allowed to do. Six things change when that connector is Sprites.
Search Console and the site, in one conversation
Sprites reads the queries a page gets impressions for before it rewrites that page’s title, and the posts that already rank before it writes a new one. A Webflow-only connector has neither.
SEO over MCPIt researches before it writes
Keyword volume, difficulty and the pages that currently rank are pulled first, so the post it drafts into your collection targets something you can actually win.
Every write is a diff, then a check
Each change is an approval card with its before and after. After it applies, Sprites reads the record back from Webflow and confirms it matches what you approved.
Scoped to one site, held by Sprites
Webflow is connected with a site API token limited to CMS, Pages and Assets. The token lives in Sprites; Claude or ChatGPT only ever talks to the Sprites endpoint.
Prompts that work verbatim
Paste any of these into a connected client. Naming Sprites matters: without it, an agent will happily answer a Webflow question from public data rather than from your account.
- With Sprites, write a post on "webflow vs framer for seo" and add it to our Webflow blog collection as a draft.
- Ask Sprites which Webflow pages have missing or duplicate meta descriptions, and propose new ones.
- Use Sprites to rewrite the SEO title and meta description on our /pricing page.
- Have Sprites find the Webflow blog posts that lost position in the last 28 days and refresh the weakest one.
- With Sprites, update the hero headline on our /features page to lead with the outcome, not the feature.
What it reads, and what it can change
Reads happen on request. Writes never happen unasked: every change to Webflow is proposed, editable, and applied only when you approve it.
What it reads
- Your Webflow pages, CMS collections, their field schemas and items
- Page content, read fresh before any copy edit
- Your asset library
- Search Console queries, impressions, clicks and average position
- Keyword volume, difficulty and what currently ranks
What it can change
- CMS items, created as drafts and published only on a separate approval
- Page titles, slugs, SEO titles, meta descriptions and Open Graph fields
- Text on existing pages, replaced node by node from a same-conversation read
- Assets uploaded from a URL or renamed, and new CMS collections
- Every one of these is an approval card first, and read back from Webflow after
The doors behind it
- write_seo_blog_post — a researched post created as a draft item in your Webflow CMS collection
- create_seo_page — page titles, slugs, SEO and Open Graph fields, or page copy, changed as a diff
- create_aeo_content — FAQ and comparison content written to be quoted by ChatGPT and AI Overviews
- research — keyword volume, difficulty and what already ranks for the target
- analyze — Search Console impressions, clicks and the pages that moved
- schedule_task — a recurring content brief or refresh that runs on its own
Webflow MCP questions
Is there an official Webflow MCP server?
Yes. Webflow runs its own MCP server at mcp.webflow.com/mcp, signed in with OAuth, one workspace per authorization. It reaches site design — elements, styles, components, interactions and custom code — and content: CMS collections and items, pages, SEO, assets, forms and the sitemap. A few canvas actions need the Webflow Designer open. Sprites is a separate server that decides what to write before it writes it.
What is the difference between Webflow’s server and Sprites?
Webflow’s server gives an agent Webflow’s controls, including the canvas, which Sprites does not touch. Sprites brings the SEO side: keyword research, Search Console and a read of your existing pages before it writes, then every change as an approval card that is checked against Webflow after it applies.
How do I connect Webflow to Sprites?
In Webflow’s site settings, generate a site API token with read and write access to CMS, Pages and Assets, and copy the Site ID from the same settings page. Paste both into Sprites once. Your AI agent then reaches Webflow through the Sprites MCP URL and never holds the token.
Will it publish to my live site without asking?
No. CMS items are created as drafts, and publishing one is a separate approval. Page metadata and copy changes are shown as a before and after and apply only when you approve them.
Can it change the design of my Webflow pages?
No. Sprites changes text on existing page elements, page metadata, assets and CMS content. Layout, styles and components stay in the Designer — Webflow’s own MCP server is the tool for those.
Which Sprites plan includes Webflow?
Publishing to Webflow is on every paid plan from Build. The SEO article writer that researches and drafts full posts is on Launch and above.
Which agents can I use it from?
Claude, ChatGPT, Codex, Cursor, Gemini, Grok and every other client that speaks remote MCP. One endpoint, one sign-in, no per-client configuration.
The rest of the connector
One URL covers every channel. These are the ones most often used beside this page.
Live performance, search-term waste, campaign builds and budget moves — every write gated.
6 doors · 13 setup guidesMeta AdsCreative fatigue per ad, learning-phase checks, new hooks previewed in the real placement.
6 doors · 13 setup guidesLinkedIn AdsCost per lead by job function, ABM account lists, sponsored content that converts.
4 doors · 13 setup guidesTikTok AdsCPA and CTR for every ad, the next creative batch, and spend moved before the CPA drifts.
5 doors · 13 setup guidesReddit AdsCommunity targeting, subreddit-native copy, and the ad groups spending without converting.
5 doors · 13 setup guidesGoogle Analytics 4Ask GA4 a question and get the answer — including which channel actually caused it.
4 doors · 13 setup guidesPostHogFunnels, retention and trends by campaign, read-only, beside the spend that bought them.
4 doors · 13 setup guidesSEO and Search ConsoleKeyword research, posts written into your CMS, and page edits that arrive as a diff.
4 doors · 13 setup guidesAI visibility (AEO)Who gets cited by ChatGPT and Perplexity for your prompts, and the pages that change it.
4 doors · 13 setup guidesShopifySEO titles across the whole catalogue, collection pages, and product copy that ships on approval.
5 doors · 13 setup guidesGoogle Business ProfilePerformance per location, the listings missing fields, and posts that keep the map pack.
4 doors · 13 setup guidesWordPressResearched posts, page edits and metadata written into WordPress as drafts you approve.
6 doors · 13 setup guidesFramerResearched posts and SEO fields written into your Framer CMS, added after you approve.
6 doors · 13 setup guidesZoho CRMPipeline and lead-source reporting beside ad spend, with approved lead, deal and note writes.
4 doors · 13 setup guidesMore on Webflow and MCP
The guides written for this channel first, then the pages that answer what this one assumes: what the protocol is, how it differs from an API, and which servers are worth connecting at all.
- Best SEO MCP serversResearch, Search Console and the CMS servers, and what stands between an edit and the live page.
- SEO automation from keyword research to publishingThe whole loop as one workflow: the keyword, the draft, the internal links and the publish.
- What is MCPThe protocol in plain English: what a server is, and what the latest revision changed.
- MCP vs APIThey are layers, not rivals. The one property that separates them.
- Best MCP servers for marketersTwelve that do marketing work, sorted by job — remote or local, read or write.
- Best Claude connectors for marketersEvery endpoint called rather than copied from a directory.
Point your agent at Webflow
One URL, one sign-in, and the next Webflow question you ask gets answered from the live account.