Allow your AI coding agents to access figma files & prototypes directly
Until 2026-09-24 this record combined several servers published from one repository. The others now have records of their own: iflow-mcp_figma-mcp. Checks from before that date include them.
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"figma-mcp-2","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Figma MCP Python [](https://badge.fury.io/py/figma-mcp) Allow your AI coding agents to access Figma files & prototypes directly. You can DM me for any issues / improvements: https://x.com/jasonzhou1993 ## Quick Installation with pipx ```bash pipx install figma-mcp ``` ### For Cursor: 1. In settings, add an MCP server using the command: ```shell figma-mcp --figma-api-key=your_figma_key ``` 2. OR Add a `.cursor/mcp.json` file in your project: ```json { "mcpServers": { "figma-python": { "command": "figma-mcp", "args": [ "--figma-api-key=your_figma_key" ] } } } ``` ### For other IDEs like Windsurf, use an MCP configuration file (e.g., `mcp_config.json`): ```json { "mcpServers": { "figma-python": { "command": "figma-mcp", "args": [ "--figma-api-key=your_figma_key" ] } } } ``` ## Install uv and set up the environment ```bash curl -LsSf https://astral.sh/uv/install.sh | sh uv venv source .venv/bin/activate uv sync ``` ## Test locally ```bash python -m figma_mcp.main ```
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.