Figma Sign-in
https://mcp.figma.com/mcp
If your call to this server failed
likely cause: auth
Up and requiring authentication (oauth_dcr) as of 16s ago. Reachable in 7 of 7 checks over 7 days.
- It uses OAuth with dynamic client registration. A 401 usually means your token expired or was revoked: re-run your client's OAuth sign-in for this server.
Latest probe
- Status
- auth_required
- Sign-in
- OAuth + DCR
- Protocol
- —
- Tools
- —
- Tool-list hash
- —
- HTTP
- 401
- Error
- —
- Latency
- 110 ms
- Checked
- 2026-10-15T10:23:08.707Z
- Registry name
- com.figma.mcp/mcp
Recent checks · 7/7 reachable in 7 days
| 16s ago | Sign-in | — | |
| 31 min ago | Sign-in | — | |
| 62 min ago | Sign-in | — | |
| 2 h ago | Sign-in | — | |
| 2 h ago | Sign-in | — | |
| 3 h ago | Sign-in | — | |
| 3 h ago | Sign-in | — | |
Registry description
The Figma MCP server brings Figma design context directly into your AI workflow.
As JSON
GET https://isitme.menloparklabai.workers.dev/v1/check?url=https%3A%2F%2Fmcp.figma.com%2Fmcp&reason=failure