Skip to content

Adonis0123/adonis-skills / skills/figma-mcp

figma-mcp

Verified

Handles every /figma-mcp invocation, which covers two jobs. First, implement or match a UI from a Figma design URL or file key (e.g. '/figma-mcp 按设计稿把这个页面做成 React', '/figma-mcp 还原度要高'): hand the visual work to figma-design-to-code and follow through to a finished screen, not just a metadata read or screenshot. Second, install, authenticate, switch accounts, recover or verify the official Figma MCP server in Codex, Claude Code, Cursor or Grok Build, keeping registration account-neutral and each host's OAuth flow authoritative. Use whoami for readiness, named-account, recovery, write and multi-host checks; for a current-account single-host read, including implement/match, let the first official read prove readiness instead of a separate identity call. Also read, filter, or audit Figma file comments (resolved review threads), which the MCP cannot read, and decide when to fall back to the Figma REST API with the user's token, e.g. on hosts outside the MCP Catalog like pi. Never copy OAuth tokens between hosts.

references/host-verification.md

View on GitHub
# Host verification

Read this reference only for installation, authentication recovery, host discovery, or multi-host acceptance. The supported endpoint is `https://mcp.figma.com/mcp`.

Before running commands, confirm the host remains listed in Figma's current MCP Catalog (<https://www.figma.com/mcp-catalog/>). These examples cover Codex, Claude Code, Cursor, and Grok Build. Do not adapt them to an unlisted client.

The registration is account-neutral. Keep the exact server identifier and endpoint when the user changes accounts; only the current host surface's OAuth grant changes. Do not create per-account MCP entries.

## Codex

Prefer the official Figma plugin in the Codex app. For the Codex CLI, use its native remote-server registration and OAuth commands:

```bash
codex mcp add figma --url https://mcp.figma.com/mcp
codex mcp login figma
codex mcp get figma
```

Do not add the server twice when the current Codex surface already exposes the official Figma plugin. App plugin authentication and CLI MCP authentication may have separate lifecycles; verify the surface actually under test.

## Claude Code

Prefer Figma's official Claude Code plugin:

```bash
claude plugin install figma@claude-plugins-official
```

For manual user-scoped registration:

```bash
claude mcp add --scope user --transport http figma https://mcp.figma.com/mcp
claude mcp login figma
claude mcp get figma
```

Claude may also expose a managed `claude.ai Figma` connector. Use the exact identifier shown by `claude mcp list` when authenticating that connector. Do not create a duplicate manual entry solely to rename it.

## Cursor

Prefer Figma's official Cursor plugin by running `/add-plugin figma` in Cursor Agent chat. For an existing manual server, use the exact identifier from the native status command:

```zsh
if command -v cursor-agent >/dev/null 2>&1; then
  figma_cursor_cli="$(command -v cursor-agent)"
elif command -v cursor-cli >/dev/null 2>&1; then
  figma_cursor_cli="$(command -v cursor-cli)"
else
  print -u2 -- "Cursor CLI not found"
fi

if [[ -n "$figma_cursor_cli" ]]; then
  "$figma_cursor_cli" mcp list
  "$figma_cursor_cli" mcp login <exact-figma-identifier>
  "$figma_cursor_cli" mcp list-tools <exact-figma-identifier>
fi
```

Resolve only the installed `cursor-agent` or `cursor-cli` executable. Do not assume a bare `agent` alias exists merely because help text uses that name. Use the resolved command without changing its MCP configuration schema. Merge the official URL into the existing user or workspace configuration; never replace other servers.

## Grok Build

Grok is listed in the catalog. Prefer Figma's official plugin repository, which Grok marks as `xAI Official`:

```bash
grok plugin list
grok plugin install https://github.com/figma/mcp-server-guide.git   # only when `grok plugin list` shows no figma plugin
```

The plugin registers the official endpoint with OAuth enabled and ships the operation skills (`figma-design-to-code`, `figma-use`, and others). Grok exposes the tools as `Figma__<tool>` through `use_tool`. Grok has no `mcp login` subcommand; let the Grok session's own OAuth prompt drive login, and use `grok mcp doctor` for connectivity diagnosis. Do not add a second manual `grok mcp add` entry when the plugin is installed.

## Run the real acceptance

This section is for readiness-only, recovery, and multi-host acceptance, so identity is part of the proof. The main skill's read-only fast path does not use it.

When no account was named, use one fresh read-only session per host with this prompt:

```text
只读验收:必须真实调用 Figma MCP 的 whoami 一次;接受当前已认证帐号,不要访问任何 Figma 文件,不要输出姓名、邮箱、plan、ID 或其他身份详情。工具成功完成只回答 FIGMA_MCP_READY;工具未暴露、需要登录或调用失败只回答 FIGMA_MCP_FAIL。
```

When the user named an account, add the target only to the ephemeral prompt and require the model to compare privately. Never persist the target in MCP configuration or skill files.

Require all five signals:

1. The official server is discovered by the host.
2. Figma tools are discovered.
3. The model issues a real `whoami` call.
4. The final sentinel agrees with the tool trace.
5. Captured output contains no private identity or file data.

For the Account result, use `CURRENT` when no target was named and the real call completed. Use `MATCH` only for an explicit target that was privately matched.

An OAuth callback, `Connected` status, or tool list is not a substitute for the real call. Report provider, plan, quota, and model-adapter failures separately from registration failures.

## Report acceptance

Report each host independently:

| Host | Server discovered | Tools discovered | Proof call | Account | Result |
| ---- | ----------------- | ---------------- | ---------- | ------- | ------ |

Use `WHOAMI` in the Proof call column for every host. Use `CURRENT` only when that proof completed without a named target, and `MATCH` only after privately matching an explicit target. Otherwise report `MISMATCH`, `UNVERIFIED`, or the exact external blocker.

## Official references

- <https://developers.figma.com/docs/figma-mcp-server/>
- <https://developers.figma.com/docs/figma-mcp-server/remote-server-installation/>
- <https://developers.figma.com/docs/figma-mcp-server/tools-and-prompts/>
- <https://www.figma.com/mcp-catalog/>
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall