u/Strong_District_9922

Hi everyone,

I've been building a free and open-source project called Figwright, mainly because I wanted a workflow that better matched how I use AI with Figma.

It started as an alternative MCP server, but over time it became something focused on fitting into existing projects rather than generating standalone examples. It can read your project's components, design tokens, icons, and coding conventions so the generated code feels closer to something you'd actually keep.

Everything runs locally, so there are no request limits, subscriptions, or cloud processing of your Figma files.

One part I especially enjoy is that it also works in the opposite direction. Besides reading designs into code, it can write back to Figma as well. You can ask your AI assistant to create layouts, sections, or UI elements, and it builds them directly on the canvas.

I also wanted the workflow to be transparent instead of feeling like a black box. There's an Activity panel that shows every MCP tool call and the payload being exchanged, plus a Debug panel that can generate a diagnostics bundle if something goes wrong.

It currently works with Claude Code, Cursor, and other MCP-compatible clients.

If this sounds interesting, I'd love for you to try it on a real project. Any feedback, bug reports, feature requests, or even just thoughts on the approach would mean a lot.

GitHub:
https://github.com/awdr74100/figwright

Hi everyone,

I've been working on a free, open-source tool called Figwright as an alternative to Figma's official MCP server, and I thought some of you might find it useful.

The biggest pain point for me was the usage limits. The official MCP server only includes 6 free requests per month. If you need more, you have to purchase a Dev seat, and even then there are still daily request limits (around 200–600 requests depending on the plan). Figwright runs entirely on your local machine, so there are no usage limits and no subscription fees.

Another thing I wanted to improve was making the generated code actually fit an existing project. Instead of producing generic output, Figwright reads your current tech stack and reuses your existing components, design tokens, icons, and project conventions. The generated code is meant to integrate into your codebase instead of becoming another template that needs rewriting. Since everything runs locally, your Figma files never leave your machine.

It's also bidirectional. The official MCP server only reads Figma into code, while Figwright can also write back to the canvas. You can ask your AI agent to create a pricing section, build an Auto Layout hierarchy, or add new UI directly inside Figma, and it'll actually construct the design for you.

One feature I personally like is that it isn't a black box. The plugin includes an Activity tab where you can inspect every MCP tool call along with the raw payload sent to the AI, so it's easy to see exactly what context was shared. If something goes wrong, the Debug tab can generate a complete diagnostics bundle that you can paste into a GitHub issue, making bugs much easier to reproduce.

It works with AI coding agents like Claude Code, Cursor, and other MCP-compatible clients.

If you're interested, give it a try on a real project. Feedback, bug reports, feature requests, and GitHub stars are all greatly appreciated.

GitHub:
https://github.com/awdr74100/figwright

Hi everyone,

I've been working on a free, open-source tool called Figwright as an alternative to Figma's official MCP server, and I thought some of you might find it useful.

The biggest pain point for me was the usage limits. The official MCP server only includes 6 free requests per month. If you need more, you have to purchase a Dev seat, and even then there are still daily request limits (around 200–600 requests depending on the plan). Figwright runs entirely on your local machine, so there are no usage limits and no subscription fees.

Another thing I wanted to improve was making the generated code actually fit an existing project. Instead of producing generic output, Figwright reads your current tech stack and reuses your existing components, design tokens, icons, and project conventions. The generated code is meant to integrate into your codebase instead of becoming another template that needs rewriting. Since everything runs locally, your Figma files never leave your machine.

It's also bidirectional. The official MCP server only reads Figma into code, while Figwright can also write back to the canvas. You can ask your AI agent to create a pricing section, build an Auto Layout hierarchy, or add new UI directly inside Figma, and it'll actually construct the design for you.

One feature I personally like is that it isn't a black box. The plugin includes an Activity tab where you can inspect every MCP tool call along with the raw payload sent to the AI, so it's easy to see exactly what context was shared. If something goes wrong, the Debug tab can generate a complete diagnostics bundle that you can paste into a GitHub issue, making bugs much easier to reproduce.

It works with AI coding agents like Claude Code, Cursor, and other MCP-compatible clients.

If you're interested, give it a try on a real project. Feedback, bug reports, feature requests, and GitHub stars are all greatly appreciated.

GitHub:
https://github.com/awdr74100/figwright

Hi everyone,

I've been working on a free, open-source tool called Figwright as an alternative to Figma's official MCP server, and I thought some of you might find it useful.

The biggest pain point for me was the usage limits. The official MCP server only includes 6 free requests per month. If you need more, you have to purchase a Dev seat, and even then there are still daily request limits (around 200–600 requests depending on the plan). Figwright runs entirely on your local machine, so there are no usage limits and no subscription fees.

Another thing I wanted to improve was making the generated code actually fit an existing project. Instead of producing generic output, Figwright reads your current tech stack and reuses your existing components, design tokens, icons, and project conventions. The generated code is meant to integrate into your codebase instead of becoming another template that needs rewriting. Since everything runs locally, your Figma files never leave your machine.

It's also bidirectional. The official MCP server only reads Figma into code, while Figwright can also write back to the canvas. You can ask your AI agent to create a pricing section, build an Auto Layout hierarchy, or add new UI directly inside Figma, and it'll actually construct the design for you.

One feature I personally like is that it isn't a black box. The plugin includes an Activity tab where you can inspect every MCP tool call along with the raw payload sent to the AI, so it's easy to see exactly what context was shared. If something goes wrong, the Debug tab can generate a complete diagnostics bundle that you can paste into a GitHub issue, making bugs much easier to reproduce.

It works with AI coding agents like Claude Code, Cursor, and other MCP-compatible clients.

If you're interested, give it a try on a real project. Feedback, bug reports, feature requests, and GitHub stars are all greatly appreciated.

GitHub:
https://github.com/awdr74100/figwright