Webflow MCP for Google Antigravity: setup in two minutes

1. Open the shared MCP config

   All four Antigravity surfaces read one file. In the IDE, click … at the top of the agent side panel, choose MCP Servers, then Manage MCP Servers, then View raw config. The file itself is ~/.gemini/config/mcp_config.json, or .agents/mcp_config.json inside a workspace.

   Antigravity IDE

   …›MCP Servers›Manage MCP Servers›View raw config

2. Add Sprites with serverUrl

   Antigravity requires serverUrl for any remote connection. Its documentation is explicit that the url and httpUrl keys other clients use are not supported here, and an entry using them is skipped rather than reported.

   ~/.gemini/config/mcp_config.json

   {
     "mcpServers": {
       "sprites": {
         "serverUrl": "https://mcp.sprites.ai/mcp"
       }
     }
   }

3. Sign in

   Antigravity registers itself with the Sprites authorization server automatically and completes the flow at its own callback. Save the file, reopen Manage MCP Servers, and connect.

   Spriteswants access on behalf of Antigravity

   • Read your connected ad accounts and site data
   • Draft campaigns, creatives and pages for your approval
   • Apply only the changes you approve

   AllowCancel

4. Use it from any surface

   Because the configuration is shared, the CLI and the SDK pick up the same server with no second step. Name the surface you are on when you follow an instruction — the products differ even though the config does not.

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.

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.

• 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.

Reopen Manage MCP Servers; Sprites is listed with its tool count, and the same entry is live in the CLI.

1. The metadata sweep

   You, in Google AntigravityWith 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.

2. Post into the CMS

   You, in Google AntigravityAsk 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.

3. Refresh a slipping page

   You, in Google AntigravityUse 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.

And on the Webflow side