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

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

Open canonical comparison link

Comparable alternatives

Shown only when capability or industry context overlaps.

Side-by-side MCP evidence comparison
Evidence fieldFramelink MCP for FigmaMCP100 RecommendedContentful MCP ServerMCP100 Recommended
Task fit
Best for
  • Providing coding agents with Figma node structure, styles, variables, and design assets needed for implementation
  • Connect compatible AI clients to Contentful's documented MCP capabilities.
Not ideal for
  • Replacing designer review or guaranteeing pixel-perfect production code from arbitrary files
  • Users who need a fully reviewed MCP100 recommendation today
Avoid when
  • The connected Figma account exposes confidential files that should not be sent to the AI client
  • Permissions, credentials, and connected data cannot be tested with least privilege
Provenance
Provenance details

Community implementation

io.github.GLips · Publisher source ↗

First-party MCP

Contentful · Publisher source ↗

Maintenance
Maintenance details

Repo: Sep 18, 2026

Package: Sep 21, 2026

Repo: Aug 7, 2026

Package: Aug 7, 2026

Popularity evidence
GitHub stars

15,901

GitHub stars · checked 2026-09-24T04:14:16.257000Z

61

GitHub stars · checked 2026-09-25T18:35:00Z

Package downloads / 30 days

288,200

package downloads / 30 days · checked 2026-09-24T04:17:38.982000Z

21,613

package downloads / 30 days · checked 2026-08-14T18:46:26.000Z

External adoption evidence
  • npm: package downloads: 350,316Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
  • npm: package downloads: 19,287Exact attributable signal.npm: package downloads · Rolling 30 days · checked 2026-08-14T18:46:26.000ZEvidence source ↗
Client coverage
Client coverage details
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Claude Code✓ Local stdio
Claude Desktop✓ Local stdio
Codex✓ Local stdio
VS Code✓ Local stdio
Cursor✓ Local stdio
OpenCode✓ Local stdio
Client coverage noteLocal stdio runs on your computer. Streamable HTTP connects to a remotely hosted MCP server.
Access and data
AuthenticationUses a personal access token through FIGMA_API_KEY or X-Figma-Token, or an OAuth bearer token. HTTP also supports per-request token headers.Contentful Management API PAT
CostThe MIT-licensed server lists no MCP fee. Figma plan and API limits, client, and model costs are separate.Contentful account/plan limits apply
PermissionsReads 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.Contentful roles + space/environment scope; PROTECTED_ENVIRONMENTS can block env-scoped writes/deletes
Data handlingFigma 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.Content/asset metadata to Contentful CMA under configured token/space/environment
Limitations
Tradeoffs
  • Structured design context reduces screenshot guesswork, but output quality still depends on file organization and granting access to Figma data.
  • Publisher attribution supports discovery, but does not replace an independent permissions and usability review.
Risk contextPrivate 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.CVE-2026-53957 fixed from 1.7.19; current source 1.21.1
Evidence date
Editorial review2026-08-112026-07-24
Candidate evidence2026-09-24T04:25:05.554391Z2026-09-25T18:35:00Z

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

Read the evidence method →