What is setup-rest-token?

A setup command for a Figma personal access token, which is a credential that lets tools read Figma files through its API. It configures the token for discovering library components.

Use it to create a read-only Figma token and add it to the tool configuration.

It helps when component searches are slow, empty, or unable to find the subscribed design-system components.

setup-rest-token — Command by atezer

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods

npx agentmods add commands/atezer/fmcp/setup-rest-token

Clone the repo

git clone --depth 1 https://github.com/atezer/FMCP

Per session 0 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,125 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. Scan, not verified.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5	$0.00000	$0.01125
Opus 5	$0.00000	$0.00562
Sonnet 5	$0.00000	$0.00225
Haiku 4.5	$0.00000	$0.00112

Measured 2d ago against content hash 8ebfb53624e0, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

setup-rest-token scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

commands/setup-rest-token.md · 114 lines

How it starts

The opening of the file, as written. The whole thing — 114 lines — stays where its author put it; the contents beside it link to each section on GitHub.

FIGMA_REST_TOKEN Setup

Kullanıcı "REST token kur", "REST token setup", "FIGMA_REST_TOKEN nasıl ayarlanır", "component discovery hızlandır" dediğinde bu komutu uygula.

Rule 24.1 REST API fallback'ini kullanabilmek ve library component'lerini 1-2 tool call'da enumerate edebilmek için Figma Personal Access Token gereklidir.

Ne zaman gerekli?

Hedef dosyada Ana-DS (veya başka DS) library'leri subscribed ama Claude component'leri bulamıyor
figma_search_components instance scan yavaş veya boş dönüyor
Token-bound primitives fallback'e düşmek yerine gerçek Ana-DS component instance kullanmak istiyorsun

Adım 1 — Figma Personal Access Token oluştur

figma.com → sağ üst profil avatarı → Settings
Sol menü → Security
Personal access tokens bölümü → Create new token
Ayarlar:
- Name: FMCP Bridge (veya dilediğin isim)
- Expiration: 90 gün (güvenlik için; sonra yenile)
- Scopes: File content (read) — SADECE read yetkisi yeterli
Generate token → token'ı hemen kopyala (sayfa yenilendiğinde bir daha görünmez!)

Token formatı: figd_XXXXXXXXXXXXXXXXXXXXXXXXX

Adım 2 — Claude Desktop config'e ekle

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Bu dosyayı aç (yoksa oluştur). Mevcut figma-mcp-bridge entry'sine env bloğu ekle:

{
  "mcpServers": {
    "figma-mcp-bridge": {
      "command": "node",
      "args": ["/Users/<user>/FCM/dist/local-plugin-only.js"],
      "env": {
        "FIGMA_REST_TOKEN": "figd_XXXXXXXXXXXXXXXXXXXXXXXXX"
      }
    }
  }
}

<user> yerine kullanıcı adını yaz (örn. abdussamed.tezer). Token'ı tırnak içinde yapıştır. Satır başında/sonunda boşluk olmasın.

Adım 3 — Claude Desktop restart

Cmd + Q ile tamamen kapat (dock'tan değil, menüden)
Yeniden aç
MCP server artık FIGMA_REST_TOKEN env var'ını okur

Adım 4 — Doğrulama

Yeni Claude Desktop chat başlat ve şunu yaz:

Read the full file on GitHub · 114 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

2d ago First seen · 114 lines · 0 tokens per session scan A 8ebfb53624e0

Subscribe to this mod's changes

setup-rest-token is a command published in the GitHub repository atezer/FMCP (9 stars, last pushed 1mo ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,125 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Backend and APIs Frontend ai claude cursor design-system design-tokens figma

setup-rest-token

Getting it into your agent

What it costs to keep this loaded

Grade A, and why

Nothing flagged

How it starts

FIGMA_REST_TOKEN Setup

Ne zaman gerekli?

Adım 1 — Figma Personal Access Token oluştur

Adım 2 — Claude Desktop config'e ekle

Adım 3 — Claude Desktop restart

Adım 4 — Doğrulama

What this file has done since we first saw it

Other commands, from other repositories

full-diagnostic

describe-component

docs-coverage

governance-review

release-check

component-audit