Memi vs Figma Context MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Memi vs Figma Context MCP
In-depth architectural comparison of the Memi and Figma Context MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Memi
Architecture & Design · Local stdio
Quality: 55/100 (Good) | Auth: No auth required
Figma Context MCP
Architecture & Design · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Verdict Summary: Choose Memi if you need specialized Architecture & Design tools running via a local process. Choose Figma Context MCP if your workspace requires Architecture & Design integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Memi when:
You need dedicated capabilities in the Architecture & Design domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Primary tools included: 46 MCP tools for design-system and interface workflows, Frontend interface audits, Tailwind token extraction.
Memi is categorized under Architecture & Design and uses a local stdio subprocess. In contrast, Figma Context MCP belongs to Architecture & Design using local stdio subprocess. Select Memi when you need capabilities focused on architecture & design and Figma Context MCP when you require tools for architecture & design.
Download SVG and PNG images used in a Figma file based on the IDs of image or icon nodes. Images will be saved relative to the server's image directory: /home/user