| FMRS | 47 / 100 · D | 64 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 |
|---|
| Security and permissions | 7 / 20 | 17 / 20 |
|---|
| Maintenance | 10 / 20 | 10 / 20 |
|---|
| Documentation | 11 / 20 | 16 / 20 |
|---|
| Setup experience | 11 / 20 | 13 / 20 |
|---|
| Best for | - Design and development teams using Cursor, Claude Code, or Codex to drive Figma with natural language
- Figma workflows requiring batch text, layout, annotation, or component-instance operations
- Users able to run Bun, a WebSocket server, and a Figma plugin
| - Teams and individuals who already manage docs/wikis in Notion and want AI clients (Claude Desktop, Cursor, etc.) to operate on that content directly
- Developers who want to self-host a local MCP server rather than use a remote hosted option
- Automation/agent workflows that need to query or update Notion database records programmatically
|
|---|
| Not for | - Static file-reading workflows that do not run the Figma plugin
- Read-only review workflows where AI must not modify the Figma document
- Workflows requiring explicitly documented remote hosting, authentication, or another transport
| - Users who want the standard-OAuth, zero-JSON-config install with active official support — Notion recommends its newer remote Notion MCP server for that
- Users uncomfortable handing a Notion integration token to a locally-run LLM client
- Use cases needing capabilities the integration deliberately excludes, such as deleting databases
- Long-term production deployments that need guaranteed maintenance, given this repo may be sunset
|
|---|
| Required permissions | - Requires running the companion development plugin in Figma
- Requires local WebSocket communication between the MCP server and the Figma plugin
- Modification tools require corresponding read/write access to the current Figma document; the exact scope depends on the tool used
| - A Notion internal integration token (NOTION_TOKEN or the Authorization value in OPENAPI_MCP_HEADERS), scoped by that integration's Capabilities (can be limited to read-only)
- Access limited to the specific pages/databases explicitly connected to the integration, not the whole workspace
- A separate bearer auth token when using the Streamable HTTP transport (--auth-token / AUTH_TOKEN)
- Network access to the Notion API
|
|---|
| Risks and side effects | - delete_node and delete_multiple_nodes remove nodes, so targets should be confirmed and results verified
- Batch text, layout, styling, and instance-override operations can affect multiple design elements
- Incorrect WebSocket channel connections can prevent communication with Figma
- Node image export has limited support and returns base64 as text
| - If the integration is granted broad read/write capabilities and connected to many pages, that content is effectively exposed to the LLM, risking data leakage or unintended edits
- Running with --unsafe-disable-auth removes bearer authentication on the HTTP transport, potentially making it reachable via DNS rebinding from pages a user visits — the README says to only use it on an isolated network
- Multi-tenant token passthrough requires careful TLS/gateway configuration; misconfiguration risks leaking or misrouting Notion tokens between tenants
- The README states this local server may be sunset in favor of the remote Notion MCP, and that issues/PRs here are not actively monitored, so long-term maintenance and security fixes are not guaranteed
- Storing NOTION_TOKEN or OPENAPI_MCP_HEADERS directly in shared client config files risks leaking the secret
|
|---|
| Supported clients | Cursor, Claude Code, Codex | Claude Desktop, Cursor, Zed, GitHub Copilot CLI |
|---|
| Tools | 40 | 9 |
|---|