| FMRS | 59 / 100 · C | 75 / 100 · B | 73 / 100 · B |
|---|
| Reliability | 8 / 20 | 13 / 20 | 12 / 20 |
|---|
| Security and permissions | 12 / 20 | 12 / 20 | 13 / 20 |
|---|
| Maintenance | 11 / 20 | 16 / 20 | 16 / 20 |
|---|
| Documentation | 15 / 20 | 17 / 20 | 16 / 20 |
|---|
| Setup experience | 13 / 20 | 17 / 20 | 16 / 20 |
|---|
| Best for | - Teams already using the OpenPencil desktop app or CLI who want AI agents to automate design workflows
- Developers who need local, offline, account-free read/write access to Figma-compatible files
- Engineering teams wanting to integrate design-file inspection or export into CI pipelines
| - Scenarios needing clean, structured web context fed to an AI assistant
- Users already on the Firecrawl platform who want to call its scraping capability directly via MCP
| - Q&A and research scenarios that need real-time, clean web content
- Users with an existing Exa account who want a zero-deployment remote option
|
|---|
| Not for | - Users who require official Figma support or an officially hosted service (OpenPencil is an unofficial third-party alternative, not affiliated with Figma)
- Scenarios needing strictly read-only, minimal-privilege access (the eval capability runs the full Figma Plugin API, i.e. arbitrary scripts)
- Non-technical users who are not comfortable with command-line tools or MCP client configuration
| - Simple static-page scraping where you don't want to depend on a third-party API and incur call costs
- Sites that explicitly disallow automated access (robots.txt)
| - Scenarios requiring a strict allowlist of search sources that can't use a third-party search service
- Budget-sensitive, high-volume search scenarios (remote/API calls may incur cost)
|
|---|
| Required permissions | - Local filesystem read/write, scoped by OPENPENCIL_MCP_ROOT (defaults to the current working directory)
- RPC access to the live document/canvas when the desktop app is running
- Local network listening on a Unix socket and 127.0.0.1:7600 when using the HTTP transport
| - Requires a Firecrawl API key to call; cost and quota are governed by the Firecrawl account
- firecrawl_agent/firecrawl_interact perform automated browser interaction, which may trigger login or form-submission flows on the target site
| - Requires an Exa API key for full functionality; OAuth login is optional in remote mode
- web_fetch_exa retrieves content from a specified URL; agent_run performs multi-step autonomous actions and needs the user to have clear expectations of Agent behavior
|
|---|
| Risks and side effects | - The eval-related capability exposes the full Figma Plugin API, allowing arbitrary scripts to run against a design file — risk of accidental or malicious data modification/deletion
- The project is explicitly under active development with acknowledged rough edges, so behavior can change between releases
- It is an unofficial, community-built Figma alternative, not endorsed by or affiliated with Figma or an MCP protocol owner
| - Bulk crawl/map tools can generate significant request volume against a target site — respect the site's rate limits and terms of service
- firecrawl_agent's interactive action chain is longer — define task boundaries clearly before running it to avoid accidentally triggering actions on a sensitive site
| - The API key should be stored carefully — avoid leaving it in plaintext in client config files on untrusted machines
- agent_run is a multi-step autonomous tool with a longer action chain — try it on low-risk tasks first
|
|---|
| Supported clients | Claude Code, Cursor, Windsurf | Claude Desktop, VS Code, Cursor, Windsurf, Zed, Amp | Claude Desktop, Claude Code, VS Code, Cursor, Windsurf, Zed, Amp, Kiro, LM Studio, Antigravity |
|---|
| Tools | 0 | 11 | 4 |
|---|