Figma

The remote server works on all seats and plans, including Starter. Figma's help centre states this plainly, and gates volume instead of access: a Starter plan allows up to 20 tool calls per month, while Dev and Full seats get 200 per day on Professional and Organization and 600 per day on Enterprise. The desktop server is the one that requires a Dev or Full seat on a paid plan.

No. Anthropic's directory labels the connector Read, but Figma documents several tools that write into your account. The generate_diagram tool creates a FigJam diagram in a new or existing file, and Figma's own rate-limit page names a category of tools that write to Figma files. Treat the Read label as understating the connector rather than describing it.

They are two different servers with different tool sets. The remote server runs at mcp.figma.com and needs only a browser sign-in, and Figma marks many tools remote only, meaning the desktop server does not have them. The desktop server runs at 127.0.0.1:3845 inside the Figma desktop app's Dev Mode. Figma recommends the remote server, which it says has the broadest feature set.

No. Figma states you can only access content you already have permission to view or edit, so the connector inherits your existing file permissions rather than widening them. There is no file picker in the OAuth flow and no per-file consent step. The boundary is your Figma seat and the plans your account belongs to, not anything you choose while connecting.

No, but the code output improves markedly if you do. Code Connect maps your Figma components to real components in your codebase, and Figma documents that the server then wraps its output in synthetic markers carrying your import statements, component snippets and prop mappings. Without it the agent still generates code, just without knowledge of your actual component library.

Figma restricts it in Claude specifically. The connector's directory listing states that get_screenshot is currently limited to returning a description of the screenshot rather than the image when called in Claude and Claude Code, and points to Figma's developer terms. In other supported clients the tool returns a PNG. This is a client-specific limit, not a plan or permission problem.

No. Figma operates an allowlist, and states that only clients listed in its MCP catalog can connect to the server. It names VS Code, Cursor and Claude Code as examples, and runs a waitlist for developers who want a new client added. This is unusual among connectors, so a standards-compliant client can still be refused at the door.

Run the whoami tool. Figma documents that it returns the authenticated user's email address, every plan that user belongs to, and the seat type held on each plan. Figma's own troubleshooting steps recommend it as the first check when a file cannot be reached, because seat type and plan membership decide both access and rate limits.