Framelink Figma Context MCP vs Slack MCP Server

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

	Framelink Figma Context MCP MCP Servers	Slack MCP Server MCP Servers
Tagline	MCP server that feeds Figma layout, styles and components into AI coding agents like Cursor and Claude Code.	Archived reference MCP server that lets Claude and other MCP clients read and post in a Slack workspace via a bot token.
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 / open-source (MIT). Requires a Slack workspace and a Slack bot token; Slack itself is free/paid.
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	Channel triage and summarisationAutomated thread digestsPosting AI-generated status updatesCross-channel search and reportingStandup and retro note postingOn-call escalation repliesUser and profile lookup for routingReaction-based workflow signallingMCP server reference implementation
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	Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke Open-source under MIT, so forking or vendoring for internal hardening is straightforward Good starting point for learning how to write your own MCP server against a REST API
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	Archived by the maintainer on 29 May 2025 — no upstream bug fixes, security patches, or Slack API compatibility updates Read-only surface for channels (public channels only by default) and no DM, private-channel, search, files, or canvas support out of the box No pagination helpers or rate-limit backoff beyond what the Slack SDK provides, so bulk history pulls in large workspaces can be fragile Requires a workspace admin to install a bot app and mint a token, which is a real blocker in locked-down enterprise Slack tenants Bot-token model means every action is attributed to the bot user, not the human operating the assistant, which complicates audit trails
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 Slack MCP Server if

✅ Official reference implementation from the modelcontextprotocol project — small, readable TypeScript that documents the MCP tool pattern well
✅ Covers the eight highest-value Slack primitives (list, post, reply, react, history, thread, users, profile) with minimal ceremony
✅ Ships as both an npx package and a Docker image, so it drops straight into Claude Desktop, Cursor, or any MCP client with a JSON config snippet
✅ Standard Slack bot-token auth (xoxb-) with clearly scoped OAuth permissions — easy to reason about and to revoke

Compare a different pair →