# 1576 Figma MCP Config D1146a31

> Figma MCP config reference

- Skill: `tools-only/1576-figma-mcp-config-d1146a31` (Agent Skill, multi-file: 3 files)
- Install (CLI): `npx skillmds@latest add tools-only/1576-figma-mcp-config-d1146a31`
- Raw SKILL.md: https://api.skillmd.com/api/skills/tools-only/1576-figma-mcp-config-d1146a31/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Design & Media
- Author: tools-only (https://skillmd.com/u/tools-only)
- Updated: 2026-09-22
- Page: https://skillmd.com/skills/tools-only/1576-figma-mcp-config-d1146a31

---

# Figma MCP config reference

Use this snippet to register the Figma MCP server in your agent's configuration as a streamable HTTP server with bearer auth pulled from your env.

## Configuration Example

```toml
[mcp_servers.figma]
url = "https://mcp.figma.com/mcp"
bearer_token_env_var = "FIGMA_OAUTH_TOKEN"
http_headers = { "X-Figma-Region" = "us-east-1" }
```

## Notes and options

- The bearer token must be available as `FIGMA_OAUTH_TOKEN` in the environment that launches your agent.
- Keep the region header aligned with your Figma region. If your org uses another region, update `X-Figma-Region` consistently.
- OAuth on streamable HTTP requires the RMCP client feature to be enabled in your agent's configuration.
- Optional per-server timeouts: `startup_timeout_sec` (default 10) and `tool_timeout_sec` (default 60) can be set if needed.

## Env var setup (if missing)

- One-time set for current shell: `export FIGMA_OAUTH_TOKEN="<token>"`
- Persist for future sessions: add the export line to your shell profile (e.g., `~/.zshrc` or `~/.bashrc`), then restart the shell or your IDE.
- Verify before launching your agent: `echo $FIGMA_OAUTH_TOKEN` should print a non-empty token.

## Setup + verification checklist

- Add the MCP server configuration to your agent's config file.
- Enable RMCP client feature if required by your agent.
- Restart your agent (CLI/IDE) after updating config and env vars.
- Ask your agent to list Figma tools or run a simple call to confirm the server is reachable.

## Troubleshooting

- Token not picked up: Export `FIGMA_OAUTH_TOKEN` in the same shell that launches your agent, or add it to your shell profile and restart.
- OAuth errors: Verify RMCP client is enabled and the bearer token is valid. Tokens copied from Figma should not include surrounding quotes.
- Network/headers: Keep the `X-Figma-Region` header; if your org uses another region, update the header consistently across config and requests.

## Usage reminders

- The server is link-based: copy the Figma frame or layer link, then ask the MCP client to implement that URL. The client will extract the node ID from the link (it does not browse the page).
- If output feels generic, restate the project-specific rules from the main skill and ensure you follow the required flow (get_design_context → get_metadata if needed → get_screenshot).