Framelink Figma Context MCP vs MCP Everything Server

A side-by-side look at pricing, capabilities, pros, cons, and our editorial scores.

	Framelink Figma Context MCP MCP Servers	MCP Everything Server MCP Servers
Tagline	MCP server that feeds Figma layout, styles and components into AI coding agents like Cursor and Claude Code.	The kitchen-sink reference MCP server that exercises every corner of the Model Context Protocol
Category	MCP Servers	MCP Servers
Pricing	Free· Free and open source (MIT). Optional Framelink hosted extras are gated behind a waitlist with no published pricing.	Free· Free and open source (MIT License). No cloud service or paid tier — you run it locally via npx, Docker, or your MCP client of choice.
Model	—	—
Editorial score	—	—
Use cases	Figma-to-React component generation in CursorMarketing landing page implementation from a Figma frameSwiftUI or Jetpack Compose screens from mobile mockupsDesign system token extraction into Tailwind or CSS variablesReconciling a Figma redesign against existing componentsGenerating HTML/CSS prototypes from a design filePixel-accurate spacing and typography audits inside an IDE agent	MCP client conformance testingRegression testing of stdio and Streamable HTTP transportsVerifying sampling round-trip behavior in a new agent hostDebugging elicitation UI in an IDE integrationReference reading for authoring a new MCP serverDemoing MCP primitives in workshops and talksSmoke-testing cancellation and progress-notification handlingValidating resource-subscription update delivery
Pros	Descriptive JSON output preserves your codebase conventions instead of forcing auto-generated React/Tailwind Roughly 25% smaller payload than Figma's official MCP, which matters for context-window-limited agents Deduplicates repeated styles and correctly represents nested component instances Works with Cursor, Claude Code, Windsurf, VS Code, Cline — any MCP client, not locked to one IDE One-line npx install; only a Figma personal access token is required MIT licensed, active repo (~15k stars), self-hostable with no vendor lock-in Keeps token names and component props, so generated code can reference your design system	Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.) Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped MIT-licensed, no telemetry, no signup, no cloud dependency Includes progress notifications and cancellation flows that most tutorial servers skip, so client cancel/timeout logic can be exercised properly
Cons	Read-only — cannot push code changes back to Figma or edit designs Quality of output still depends on how disciplined the Figma file is (auto-layout, named styles, components) Requires a Figma personal access token per developer; no team-level auth flow Framelink hosted tier is a waitlist with no public pricing, so long-term commercial model is unclear Very large or deeply nested files can still blow past model context if you request whole pages instead of frames	Explicitly not useful for end users — it does not do anything a human would actually want done Feature drift means some primitives (SEP-1686 Tasks, elicitation) may not yet be implemented in every client, producing red herrings during testing Documentation is a single features.md; there is no guided tour that maps each tool to the spec section it exercises TypeScript-only reference — Python or Rust client authors have to translate patterns themselves Sampling and elicitation flows depend on the client honoring them, so a silent client makes it hard to tell whether the server or the client is at fault
Website	github.com	github.com

Pick Framelink Figma Context MCP if

✅ Descriptive JSON output preserves your codebase conventions instead of forcing auto-generated React/Tailwind
✅ Roughly 25% smaller payload than Figma's official MCP, which matters for context-window-limited agents
✅ Deduplicates repeated styles and correctly represents nested component instances
✅ Works with Cursor, Claude Code, Windsurf, VS Code, Cline — any MCP client, not locked to one IDE

Pick MCP Everything Server if

✅ Only server that exercises the full MCP feature matrix in one place — tools, resources, prompts, sampling, elicitation, roots, logging, subscriptions, and Tasks
✅ Maintained by the Model Context Protocol project itself, so behavior tracks the spec as it evolves (SEP-1686 Tasks, Streamable HTTP, etc.)
✅ Runs anywhere an MCP client runs — npx, Docker, Claude Desktop, VS Code, Cursor, Windsurf — with stdio or HTTP transports
✅ TypeScript source is short and readable, making it a de-facto reference for how each handler should be shaped

Compare a different pair →