Vibeleaderboard
Index / tool
Visit github.com
Category
Developer Tools
Rank
No. 4075Tools index

Previous survey · No. 3797 ·

Pricing
Open Source
Type
TOOL
Use case
Design & Media
GitHub
2 stars
Latest release
v0.2.0
Date

About

figma-server gives an AI agent full access to Figma over the Chrome DevTools Protocol (CDP), as an alternative to Figma's MCP server. The author argues this matters because Figma's MCP server only accepts clients listed in its MCP Catalog, which limits which agents can work with a user's files.

At a glance

figma-server lets an agent control Figma through a dedicated signed-in Chromium profile. Consider it only if you need browser-level actions from a custom client and can isolate the files and credentials that client can reach.

Good fit

Developers evaluating custom Figma automation in a disposable workspace with a trusted agent.

Consider something else when

Skip it if your approved Figma integration already covers the job, or if you cannot isolate the browser profile from real design files.

Start here

For a controlled trial, sign into a dedicated profile with access to one disposable file. Ask the agent to inspect that file before attempting any edits, then check exactly what content the client receives.

Cost and requirements

Apache-2.0 project. The documented setup requires Node.js 22.16 or later, Chromium, a graphical desktop for sign-in and a Figma account with access to the file.

Limits to know

The agent can click, type and run JavaScript in a signed-in browser. Raw browser commands can bypass the server’s managed file locks, and returned content can reach the agent’s model provider.

Tags

figmacdpai-agentsmcpdesigntypescript

Tech Stack

Node.jsTypeScript

Comments (0)

No comments yet

Editorially curated, with community endorsements as a secondary signal. Corrections welcome.