Field-by-field comparison

Compare the evidence before choosing an MCP.

Each signal stays separate, missing facts remain visible, and the column order follows your selection.

MCPs in this comparison

WebflowFigma MCP

Uncheck an MCP to remove it. Comparing two or three keeps each signal in its own row.

Comparable alternatives

Azure MCP ServerMCP100 RecommendedChrome DevTools MCPMCP100 RecommendedContext7 MCPMCP100 RecommendedGrafana Cloud MCPMCP100 RecommendedGoogle MCP Toolbox for DatabasesMCP100 RecommendedGoogle Search Console MCP Server for SEOsMCP100 Recommended

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	WebflowShortlist candidate	Figma MCPMCP100 Recommended
Task fit
Best for	Webflow designers/developers who want AI-assisted page, CMS and site operations while retaining Webflow role controls.	Turning selected Figma frames into implementation context Design-system teams using variables, components, and Code Connect Human-supervised creation or modification of native Figma content
Not ideal for	Users who need a broadly proven, low-risk, Recommended-grade integration with longer MCP production history.	MCP clients outside Figma's supported catalog Teams expecting one-click pixel-perfect production code Headless automation that cannot complete user OAuth
Avoid when	Avoid granting an AI client write/publish authority on a production site unless the connected Webflow role is intentionally scoped.	Proprietary design content cannot be exposed to the selected AI client or model Canvas writes cannot be reviewed before execution A stable long-term zero-cost commitment is required
Provenance
Provenance details	First-party MCP com.webflow · Publisher source ↗	First-party MCP Figma · Publisher source ↗
Maintenance
Maintenance details	Repo: Not documented Package: Not documented	Repo: Not documented Package: Not documented
Popularity evidence
GitHub stars	140 GitHub stars · checked 2026-10-21	Not documented
Package downloads / 30 days	5,483 package downloads / 30 days · checked 2026-10-21	No reliable download data
Client coverage
Client coverage details	Not documented	Claude Code✓ Streamable HTTP Claude Desktop✓ Streamable HTTP Codex✓ Streamable HTTP VS Code✓ Streamable HTTP Cursor✓ Streamable HTTP OpenCode✓ Streamable HTTP
Client coverage note	Local stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
Authentication	Publisher authorization/OAuth-style account connection to Webflow; exact scopes must be preserved from the reviewed Webflow evidence.	The recommended remote server at https://mcp.figma.com/mcp uses user OAuth. Desktop mode relies on the signed-in Figma desktop application and its local endpoint.
Cost	Webflow plan requirements and limits apply; MCP availability does not remove normal Webflow plan/API constraints.	Figma documents the MCP feature as free during its current beta and says it is expected to become usage-based paid. Underlying Figma plans and plan-specific features may also apply.
Permissions	The server respects the connected user's existing Webflow site/workspace role. Mutating actions can change site/CMS content and may include publish-related workflows depending on the exposed tool and account permission.	The connected user's Figma identity and existing file permissions govern access. The current remote MCP is not purely read-only: Write to Canvas can create or modify design content for users or seats with required edit authority, while read-only design-context workflows remain available without edit authority.
Data handling	Site structure, CMS content and other Webflow account data requested through tools can be sent to the connected AI client/provider.	The remote service retrieves design nodes, components, variables, layouts, and potentially Make or Code Connect resources and returns them to the MCP client. Desktop mode can write downloaded assets into the local project.
Limitations
Tradeoffs	Official MCP documentation and useful CMS/site workflows, but production write/publish scope and adoption evidence need validation.	The hosted endpoint is easiest to connect and has the broadest feature set, but authorized design context passes through Figma and the connected AI workflow. The desktop server is locally reachable through the Figma app, but it is intended for narrower organization and enterprise use cases. Code Connect can improve component reuse but requires additional design-system setup.
Risk context	Primary risk is production site/CMS mutation under the connected user's Webflow permissions.	Private designs can be disclosed through tool results, and write-enabled tools can change shared design files. Restrict accessible files, review OAuth consent, require confirmation for writes, and inspect downloaded assets before committing them.
Evidence date
Editorial review	2026-10-21	2026-07-24
Candidate evidence	2026-10-21T00:00:00Z	2026-09-24T04:25:05.554391Z

Popularity, maintenance, fit, permissions, and client support are independent evidence fields.

Read the evidence method →