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

WebflowFramelink MCP for Figma

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

Comparable alternatives

Azure MCP ServerMCP100 SelectedChrome DevTools MCPMCP100 SelectedContext7 MCPMCP100 SelectedGrafana Cloud MCPMCP100 SelectedGoogle MCP Toolbox for DatabasesMCP100 SelectedGoogle Search Console MCP Server for SEOsMCP100 Selected

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence field	WebflowWatchlist candidate	Framelink MCP for FigmaMCP100 Selected
Task fit
Best for	Webflow designers/developers who want AI-assisted page, CMS and site operations while retaining Webflow role controls.	Providing coding agents with Figma node structure, styles, variables, and design assets needed for implementation
Not ideal for	Users who need a broadly proven, low-risk, Selected-grade integration with longer MCP production history.	Replacing designer review or guaranteeing pixel-perfect production code from arbitrary files
Avoid when	Avoid granting an AI client write/publish authority on a production site unless the connected Webflow role is intentionally scoped.	The connected Figma account exposes confidential files that should not be sent to the AI client
Provenance
Provenance details	First-party MCP com.webflow · Publisher source ↗	Community implementation io.github.GLips · Publisher source ↗
Maintenance
Maintenance details	Stale Repo: Not documented Package: Not documented	Repo: Aug 7, 2026 Package: Jun 18, 2026
Popularity evidence
GitHub stars	Not documented	15,658 GitHub stars · checked 2026-08-14T18:46:26.000Z
Package downloads / 30 days	No reliable download data	350,316 package downloads / 30 days · checked 2026-08-14T18:46:26.000Z
External adoption evidence	Not documented	npm: package downloads: 350,316Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details	Not documented	Claude Code✓ Local stdio Claude Desktop✓ Local stdio Codex✓ Local stdio VS Code✓ Local stdio Cursor✓ Local stdio OpenCode✓ Local stdio
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.	Uses a personal access token through FIGMA_API_KEY or X-Figma-Token, or an OAuth bearer token. HTTP also supports per-request token headers.
Cost	Webflow plan requirements and limits apply; MCP availability does not remove normal Webflow plan/API constraints.	The MIT-licensed server lists no MCP fee. Figma plan and API limits, client, and model costs are separate.
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.	Reads Figma file and node data through the Figma API and downloads PNG, SVG, or GIF assets into a configured local image directory; no Figma write capability is documented.
Data handling	Site structure, CMS content and other Webflow account data requested through tools can be sent to the connected AI client/provider.	Figma metadata and API responses are returned to the MCP client; raw tools write figma-raw.json locally and image tools save assets locally. Telemetry sends server, platform, session, and event metadata by default; retention is not documented.
Limitations
Tradeoffs	Official MCP documentation and useful CMS/site workflows, but production write/publish scope and adoption evidence need validation.	Structured design context reduces screenshot guesswork, but output quality still depends on file organization and granting access to Figma data.
Risk context	Primary risk is production site/CMS mutation under the connected user's Webflow permissions.	Private design data and assets can reach the MCP client or model and local raw logs; telemetry adds metadata transmission. Protect tokens, restrict the image directory, and review downloaded and raw files.
Evidence date
Editorial review	2026-09-13T00:00:00Z	2026-08-11
Candidate evidence	2026-09-13T00:00:00Z	2026-08-14T18:46:26.000Z

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

Read the evidence method →