Home / MCP registry index / Topics / Figma
Figma MCP servers, with their tools checked
Every server in the official MCP registry that mentions Figma, with a public endpoint, read the way an MCP client reads it and checked for tool poisoning. The list updates as the registry does, and each server is read again every week.
10 listed. We have read the tools of 0 so far; the others want credentials first, could not be reached, or are still waiting for their first read.
These servers act inside an account you own, usually with a token you give them. Prefer the narrowest access the tools need, and check which tools can send, post or delete.
| DS Manager com.shadcndesign.manager/ds-manager | needs credentials to list tools 2026-10-21 |
| Lenny's Podcast Transcripts io.usewire/lennys-podcast | not reachable 2026-10-22 |
| Figma MCP Server com.figma.mcp/mcp | not read yet |
| com.lightsyncpro/lsp com.lightsyncpro/lsp | not read yet |
| Whoogy com.whoogy/whoogy-mcp | not read yet |
| Anima MCP Server io.github.AnimaApp/anima | not read yet |
| io.github.KyleTaggart/lsp io.github.KyleTaggart/lsp | not read yet |
| Figma io.github.pipeworx-io/figma | not read yet |
| Figma URL Shape io.github.sadri-dridi/figma-url-shape | not read yet |
| Commentify one.commentify/commentify | not read yet |
Choosing one
Open a server's page to see the tools it advertises, whether it sets instructions for the model, and our latest read. A clean read means our rules found nothing, not that a server is harmless; still check what access it asks for. To check one that is not listed, paste its URL into the free MCP server check.
Related: GitHub · GitLab · Notion · Slack · Discord · Email · Calendar · Google Workspace · all topics