Figma Context MCP vs Memi

In-depth architectural comparison of the Figma Context MCP and Memi 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.

Which MCP Server Should You Choose?

Choose Figma Context MCP when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Figma Context MCP Details

Choose Memi when:

• You need dedicated capabilities in the Developer Tools domain.
• You prefer local stdio subprocess transport architecture.
• Your security boundary fits: No auth required (Free / Open Source).

Explore Memi Details

Feature & Specification Comparison

Specification	Figma Context MCP Developer Tools	Memi Developer Tools
Summary	MCP server to extract Figma design information and convert it to mostly css for coding agents.	Memi is the read-only design engineering audit and skill layer for coding agents.
Category & Scope	Developer Tools	Developer Tools
Quality signal

Tools & Capabilities Breakdown

Ready-to-Paste Client Configurations

Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).

{
  "mcpServers": {
    "figma-context-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@tmegit/figma-to-code-mcp",
        "--figma-api-key=YOUR-KEY",
        "--stdio"
      ]
    }
  }
}

{
  "mcpServers": {
    "memi": {
      "command": "npx",
      "args": [
        "-y",
        "@memi-design/cli@latest"
      ]
    }
  }
}

Related MCP Server Comparisons