cursor-talk-to-figma-mcp vs mcp-atlassian
cursor-talk-to-figma-mcp: This project provides a Model Context Protocol (MCP) integration between Cursor AI and Figma, enabling AI-powered programmatic interaction with Figma designs. It allows Cursor to read design information, modify elements, and automate various design tasks through a WebSocket server and a Figma plugin.; mcp-atlassian: MCP Atlassian is a Model Context Protocol server designed for seamless integration with Atlassian's Confluence and Jira products. It enables AI assistants to interact with both Cloud and Server/Data Center deployments of these platforms.
TL;DR
Automating repetitive design tasks like bulk text replacement and instance override propagation.
- You run Jira or Confluence on Server or Data Center (Jira 8.14+, Confluence 6.0+), which the hosted official server does not cover.
- You want to run the server yourself with `uvx mcp-atlassian` and keep it on your own machine or network.
- You want JQL and CQL search, issue transitions and an SLA calculation tool in one MIT-licensed server.
- You need Bitbucket, Jira Service Management or Compass: the README covers Jira and Confluence.
- You do not want API tokens stored in your MCP client config: this server reads them from environment variables.
- You are on Python 3.14: the README says it is not supported yet.
Side-by-Side Comparison
Features
Use Cases
Best For
FAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.