| FMRS | 47 / 100 · D | 66 / 100 · C | 58 / 100 · C |
|---|
| Reliability | 8 / 20 | 8 / 20 | 13 / 20 |
|---|
| Security and permissions | 7 / 20 | 15 / 20 | 11 / 20 |
|---|
| Maintenance | 10 / 20 | 15 / 20 | 10 / 20 |
|---|
| Documentation | 11 / 20 | 15 / 20 | 13 / 20 |
|---|
| Setup experience | 11 / 20 | 13 / 20 | 11 / 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
| - Developers, content creators, and project teams using Atlassian Cloud
- Teams that want Atlassian access inside ChatGPT, Claude, Cursor, or VS Code
- Users who need natural-language search, write, and cross-product workflows
| - Internal collaboration workflows that need channel history or team notifications
- Development teams testing message automation in a non-production workspace
|
|---|
| 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 without an Atlassian Cloud site or relevant product permissions
- Deployments requiring a self-hosted MCP server
- Users unwilling to grant an AI client access to Atlassian data or actions
- Jira Service Management or Bitbucket Cloud workflows requiring OAuth authentication
| - Organizations that prohibit model access to internal chat history
- Workspaces that cannot tightly restrict bot channels and OAuth scopes
|
|---|
| 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
| - Jira and Confluence provide read, write, and search permission groups
- Jira Service Management provides read and write access through API tokens only
- Bitbucket Cloud provides read and write access through scoped API tokens only
- Compass is available through OAuth 2.1 only
- The first OAuth installer for a site must have access to the Atlassian apps requested by the MCP scopes
- Organization administrators can manage domain controls, API-token authentication, app access, and audit logs
| - A Slack Bot Token and Team ID
- Least-privilege OAuth scopes for channel history, messages, or reactions
|
|---|
| 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
| - AI clients can perform Jira, Confluence, Jira Service Management, Bitbucket, and Compass actions on the user’s behalf
- Prompt injection, indirect prompt injection, and tool-poisoning attacks may cause data exfiltration or unintended changes
- Use least privilege, scoped tokens, and minimal project or workspace access
- Require human confirmation for high-impact or destructive actions and monitor audit logs
| - Channel history may contain internal or personally sensitive information
- Messages and reactions are visible to real members; confirm channel and content before writes
|
|---|
| Supported clients | Cursor, Claude Code, Codex | OpenAI ChatGPT, Claude, Cursor, Visual Studio Code (GitHub Copilot), GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote | Claude Desktop, Cursor, Cline |
|---|
| Tools | 40 | 0 | 4 |
|---|