Figma Console MCP Removes the 20-Call Limit: Run Your Agent With Figma for Free

You want to give an agent access to Figma — and immediately hit a wall: on the free plan, the official MCP allows just 20 calls per month. For real design work, that is enough for a single failed evening. The author of the Tips AI channel found a workaround on GitHub, and it looks surprisingly elegant.

What's the trick

The official MCP counts every request and cuts it off at the quota. But Figma also has the Plugin API — the very one that ordinary plugins run on. It has no limits on the number of calls. The open-source project figma-console-mcp does a simple thing: it launches a bridge plugin inside Figma, and the agent communicates with it over the MCP protocol. To the agent it looks like a regular MCP server, and to Figma it looks like a regular plugin doing something to the document.

Imagine the task: "build a login screen, add three button states and link them with transitions in the prototype." On the free plan with the official MCP, you would burn through the quota in one or two attempts, especially since the agent also makes mistakes and restarts steps. Through the bridge, the same operations go through the Plugin API, and the counter doesn't tick.

What the agent can do

According to the author's description, the functionality nearly matches the official server. The agent can create and edit frames, shapes and text, set up prototype transitions, and follow your edits in real time. This is handy when you draw by hand and the agent picks up the context and finishes the routine work: aligning the grid, renaming layers, multiplying component variants. The project claims around 130 tools in total, so practically everything Figma itself can do is available to the agent too.

How to install it

Setup takes minutes. You need the desktop version of Figma — the bridge won't work in the browser. Next, you give your agent the repository link, and it creates the Desktop Bridge plugin itself. You open the project you need and enable the plugin via the menu Plugins → Development → Figma Desktop Bridge. You can even skip doing this by hand and ask the agent to walk you through all the steps. It works on both macOS and Windows.

Limitations and takeaways

The main drawback, which the author names himself: there is no Code Connect, meaning the link between design components and the codebase. If your workflow relies on the agent taking a component from Figma and finding its implementation in the repository, the free bridge won't replace that. You will have to either pay for official access or describe the mapping manually.

There are also caution points. This is a third-party plugin, which by definition has access to your files, and you are giving the agent the ability to modify the document. Before running it on a production project, you should review the code and start experimenting on a copy of the file. Moreover, the absence of limits is an observation by the post's author, not a guarantee from Figma: the company may change the Plugin API rules, and the scheme will stop working as smoothly.

The practical takeaway for developers and product managers is simple. If you want to try agents in your design process and aren't ready to pay for a plan just for an experiment, figma-console-mcp is the cheapest way. Start with a small task such as generating screen variants or bulk-renaming layers, assess the quality, and decide whether you need the full official MCP with Code Connect. It is also a good example of a general technique: when a product places tight API limits on agents, look for a neighboring interface — plugins, extensions, scripts — where there are fewer restrictions.