Figma's third quarter 2026 results report that total MCP usage grew 3x quarter over quarter and write-back usage grew 4x, according to the company's press release dated November 4, 2026. For a product manager, that means Figma reports growing MCP usage, including a separately reported write-back figure that the documents I read do not define. These are vendor-reported figures, and the same release lists non-GAAP gross margin at 82%.
TL;DR: Figma reports that total MCP usage grew 3x and write-back usage grew 4x quarter over quarter in Q3 2026, and that 65% of Paid Customers with more than $10,000 in ARR were using the Figma agent weekly as of October 31. Non-GAAP gross margin was 82%, compared with 85% in Q2 (derived by comparing the two releases). The documents I read do not define write-back or state how it relates to total MCP usage. The figures are company-reported.
Key Takeaways
- Usage growth: Figma says total MCP usage grew 3x and write-back usage grew 4x quarter over quarter in Q3. The documents I read do not define write-back or state how it relates to total MCP usage.
- Agent adoption: The company says 65% of Paid Customers with more than $10,000 in ARR used the Figma agent weekly, and over 80% consumed AI credits, as of October 31.
- Margin context: Non-GAAP gross margin was 82% in Q3, against 85% in Q2 (derived by comparing the two releases), and the prepared remarks mention covering the inference cost of the Figma agent.
- Specs and code: Code Layers began an open beta on October 14, and Figma describes Specs as a place for markdown on the canvas.
What did Figma report about MCP usage in Q3 2026?
Figma reported that total MCP usage grew 3x quarter over quarter and write-back usage grew 4x. The press release states this in one sentence, and the quarter ended September 30, 2026.
The prepared remarks add context. They say the Figma MCP server was the company's "fastest-growing product by growth in weekly active users" during Q3. The remarks give approximately 1 million weekly active users as of "today". They also say about half of new Pro teams used the MCP server in Q3, and that MCP drives 5% of credit consumption.
The release gives multipliers for MCP usage, not absolute usage counts. A 3x jump from a small base and one from a large base mean different things, and the release does not say which applies.
What is write-back, and why does the 4x figure matter?
The press release reports write-back usage next to total MCP usage, 4x against 3x. The documents I read do not define write-back or state how it relates to total MCP usage, so I cannot say whether it is included in the total.
The prepared remarks list new MCP capabilities, including the ability to generate code layers, images or push a markdown file into Figma Specs. Those actions put content onto the canvas, and they are the nearest description of write-back in the pages I read, though the remarks do not tie them to the figure.
Figma describes Specs as "a medium for markdown that lives directly on the Figma canvas" that works with both human and agent collaborators.

How many customers use the Figma agent?
As of October 31, 2026, 65% of Paid Customers with more than $10,000 in ARR were using the Figma agent weekly, and over 80% were consuming AI credits, per the press release.
The Q2 release says that as of June 30, 2026, over 80% of the same customer group were consuming AI credits weekly. The remarks say the Figma agent became generally available on October 6, and the press release dates the Code Layers open beta to October 14, 2026.
What does the gross margin say about the cost of AI usage?
Non-GAAP gross margin was 82% in Q3 2026, and GAAP gross margin was 80%, according to the press release. The Q2 release reports 85% non-GAAP and 84% GAAP. The 85% to 82% change is derived by comparing the two releases, because the Q3 release gives no Q2 margin.
The prepared remarks say that while gross profit dollars grew, "we made the decision in Q3 to cover the cost of inference for the Figma agent ahead of its GA launch on October 6th." They also say Figma reduced the average cost per message across agent messages. The passages I read do not attach a margin number to either statement, so I will not claim how much of the change either one explains.
| Metric | Q2 2026 | Q3 2026 | Source |
|---|---|---|---|
| Revenue | $370.1 million | $391.4 million | Q2 release and Q3 release |
| Non-GAAP gross margin | 85% | 82% | Q2 release and Q3 release |
| GAAP gross margin | 84% | 80% | Q2 release and Q3 release |
| Paid Customers above $10,000 ARR consuming AI credits weekly | Over 80% (June 30) | Over 80% (October 31) | Q2 release and Q3 release |

What could a PM take from this?
The numbers give a PM three questions to ask about their own team, and these are my reading, not Figma's advice. Which of your specs and designs do coding agents already read? Which can they now change? And who reviews a change that an agent made?
The write-back figure, whatever it covers, points to the second: a file an agent can edit needs an owner and a review step, as a shared document does.
The third is a budget question. Figma's gross margin moved from 85% to 82% (derived by comparing the two releases) in a quarter in which it says it covered inference costs for its own agent, and it reports repricing its credits in August. The pages I read do not say what Figma charges per MCP call.
Frequently Asked Questions
What is the Figma MCP server?
The remarks name Notion, Xcode and Meta's AI agent Muse among its partners and say it can generate code layers, images or push a markdown file into Figma Specs. I found no formal definition in the Q3 sources.
Did Figma report that MCP usage tripled?
Yes. The Q3 press release says total MCP usage grew 3x quarter over quarter and write-back usage grew 4x.
Is the 82% gross margin a sign of a problem?
The sources do not say so. The press release reports 82% non-GAAP gross margin, down from 85% in Q2 (derived by comparing the two releases). The prepared remarks mention covering inference costs for the Figma agent and a lower average cost per message. The pages I read give no margin target.
Conclusion
Figma's Q3 2026 release gives PMs a vendor-reported signal of growing MCP usage and a faster-growing write-back figure that the documents I read do not define. It also shows a margin that moved from 85% to 82% in the same period (derived by comparing the two releases). Treat the 3x and 4x multipliers as claims from one vendor, check how your own specs are exposed to agents, and ask your tool vendors how agent usage is priced before it shows up on an invoice.
Learn from me

Agentic AI for Product Managers, my Maven cohort. Learn how to design, evaluate, and ship reliable AI systems: the technical fluency PMs need to lead agentic products, no engineering background required. Join the next cohort →
Hire us
Traversaal.ai. We're a team of forward deployed engineers solving the toughest AI problems for Fortune 100 companies: document intelligence, agentic data platforms, and real-time web intelligence, deployed in production. Work with our team to deploy your next agentic ecosystem. Talk to Traversaal.ai →
Join us
Want to solve these problems with us? We're always looking for forward deployed engineers who want to ship production AI. jobs@traversaal.ai
