Is the Figma MCP Server Free? Plans, Limits, and Setup
Yes, Figma MCP access is currently free in beta, but monthly tool-call limits and seat type determine how much you can use.
Yes. Figma says its remote MCP server is available on all seats and plans and is currently free during the beta period. Free access is limited: Starter users and View or Collab seats on paid plans can make up to six MCP tool calls per month. Dev and Full seats on Professional, Organization, or Enterprise plans use per-minute limits based on Figma REST API Tier 1 limits. Figma says the feature will eventually become usage-based paid, so “free” is the current beta status, not a permanent price promise.
Figma’s remote MCP endpoint is https://mcp.figma.com/mcp. Figma recommends the hosted remote server for most users. You connect it through an MCP-capable editor or application, sign in with your Figma account, and provide a link to a file or selected object that you are allowed to view or edit.
What “free” means for each Figma user
| User or feature | Current access | Practical meaning |
|---|---|---|
| Remote MCP server | Available on all seats and plans; currently free during beta | You can try the hosted server without purchasing a paid Figma seat, subject to usage limits. |
| Starter plan | Up to 6 MCP tool calls per month | Suitable for occasional experiments, not unlimited automation. |
| View or Collab seat on a paid plan | Up to 6 MCP tool calls per month | A paid team plan does not automatically give every seat the higher allowance. |
| Dev or Full seat on Professional, Organization, or Enterprise | Per-minute limits following Figma REST API Tier 1 limits | Your effective capacity depends on the API limit regime; Figma can change these limits. |
| Write to canvas | Full and Dev seats on paid plans | Editing designs through MCP requires an eligible paid seat. Dev seats can write only in drafts and are otherwise read-only. |
| Desktop MCP server | Dev or Full seats on paid plans | This local option is narrower than the remote server and is not required for basic remote access. |
The commonly quoted figure is up to six tool calls per month for Starter users and View or Collab seats on paid plans. That is a monthly allowance, not six files, six prompts, or six minutes. A single MCP interaction can involve more than one operation depending on the client and tool being used.
Remote versus desktop MCP
Remote server
The remote server is Figma’s broad-access option. It runs at mcp.figma.com/mcp, works through an MCP-capable client, and is available across seats and plans. Figma recommends it for most users. Authentication happens with your Figma account, and the file or object link must point to content your account can access.
Desktop server
The desktop server is a local configuration intended for specific paid-plan use cases. Figma lists Dev and Full seats on paid plans as eligible. You do not need a special hardware device; “desktop” refers to the local server route in the Figma desktop workflow.
How to connect the remote Figma MCP server
- Use an editor or application that supports remote MCP servers.
- Add Figma’s remote endpoint:
https://mcp.figma.com/mcp. - Authorize the connection with your Figma account when the client opens Figma authentication.
- Give the MCP client a Figma file link or selected-object link.
- Confirm that your account has permission to view or edit the referenced content.
Client configuration syntax differs between applications, so use the MCP client’s documented server-settings format. The value that must remain the same is the remote URL:
{
"url": "https://mcp.figma.com/mcp"
}This snippet shows the server value only. Your client may require a different surrounding key such as mcpServers, an authentication method, or a UI-based sign-in step.
What the free allowance is enough for
- Learning: Ask an MCP-capable editor to inspect a small number of files or objects.
- Occasional handoffs: Pull design context into code when a project changes infrequently.
- Prototype workflows: Validate whether your editor and prompts produce useful design context.
The allowance may be too small for repeated daily extraction, automated design reviews, or a team that shares one limited seat type. For those workflows, check whether your account uses a Dev or Full seat on a qualifying paid plan and plan around the applicable per-minute limits.
What is not included by default
- Free beta access does not mean unlimited calls.
- A paid organization plan does not give View or Collab seats the Dev or Full allowance.
- Remote access does not automatically grant permission to every Figma file.
- Basic remote access does not imply write-to-canvas access.
- Figma has not announced a future usage price or date in the cited materials.
Troubleshooting
The client cannot connect to the server
Check that the endpoint is exactly https://mcp.figma.com/mcp, that your client supports remote MCP servers, and that the client has completed Figma authentication. Remove accidental whitespace or a trailing path copied from another service.
Authentication succeeds but the file cannot be read
The signed-in Figma account may not have permission to view the file or selected object. Open the link in Figma with the same account and request access from the file owner if necessary.
You reached the limit after only a few requests
Starter users and View or Collab seats on paid plans have an allowance of up to six tool calls per month. Check the seat type, not only the organization’s plan name. Dev and Full seats on qualifying paid plans follow a per-minute limit regime instead.
A write operation is rejected
Write-to-canvas is available to Full and Dev seats on paid plans. Dev seats can write only in drafts and remain read-only elsewhere. Use a permitted draft or switch to an eligible Full seat when your workflow requires editing.
The desktop option is unavailable
Figma lists the desktop server for Dev or Full seats on paid plans. Use the remote server if your seat or plan does not meet that requirement.
The client asks for a different configuration shape
MCP clients expose different settings screens and JSON layouts. Keep the Figma URL unchanged, then follow your client’s format for the surrounding configuration and authentication flow.
Reliability, limits, and future pricing
Figma describes the remote MCP server as generally available, while its guide still describes free access as a beta-period offer. Those statements can both be true: generally available does not mean unlimited or permanently free. Figma also says the feature will eventually become usage-based paid. Recheck Figma’s current documentation before committing a production workflow to today’s allowance or eligibility rules.
For capacity planning, record your seat type, plan, number of MCP interactions, and whether operations are read-only or write-to-canvas. Do not substitute a made-up numeric quota for Dev or Full seats; the cited Figma material refers to Tier 1 REST API limits and reserves the right to change them.
Or skip the browser setup
If your goal is to generate screenshots of web pages for documentation, visual checks, or agent workflows, ScreenshotNeo is the alternative to try first. It accepts one GET request and returns a PNG, JPEG, WebP, or PDF. Before capture it accepts cookie and consent banners and removes more than 60 known consent platforms, newsletter popups, and chat widgets. Bot checks, blank pages, timeouts, failed loads, and cache hits are not billed, and response headers identify the page verdict and billing result. ScreenshotNeo also provides an MCP server with take_screenshot, get_page_info, and capture_pdf tools for Claude, Cursor, and other MCP clients.
See the ScreenshotNeo API documentation for all options. A one-call example:
curl -G "https://api.screenshotneo.com/v1/shot" -d access_key=YOUR_API_KEY --data-urlencode url=https://stripe.com -o shot.webpimport requests
r = requests.get("https://api.screenshotneo.com/v1/shot", params={"access_key": "YOUR_API_KEY", "url": "https://stripe.com"}, timeout=90)
open("shot.webp", "wb").write(r.content)const q = new URLSearchParams({ access_key: 'YOUR_API_KEY', url: 'https://stripe.com' });
const res = await fetch(`https://api.screenshotneo.com/v1/shot?${q}`);ScreenshotNeo includes full-page capture, element capture, device presets, custom CSS and JavaScript, waits, request blocking, headers and cookies, PDF output, caching, signed links, async jobs, bulk capture, and usage reporting on every plan. The Free plan includes 1,000 screenshots per month with no card; paid plans start at $5 for 3,000. Create a free ScreenshotNeo account.
FAQ
Is the Figma MCP server free on a paid Figma plan?
Yes, remote access is currently free during beta, but View and Collab seats are limited to up to six tool calls per month.
Do I need a paid Figma seat?
No for the remote server’s basic access. Figma lists the remote server on all seats and plans. Paid Dev or Full seats are needed for the higher per-minute limit regime and write-to-canvas eligibility.
Is six tool calls the same as six prompts?
No. It is Figma’s stated monthly MCP tool-call allowance for Starter users and View or Collab seats. The number of underlying calls depends on the client operation.
Will Figma always keep MCP free?
No promise has been made. Figma says it will eventually become usage-based paid, without giving a price or date in the cited guidance.
Which server should most users choose?
Figma recommends the hosted remote server for most users. The desktop server is a narrower local option for eligible Dev and Full seats on paid plans.
