| FMRS | 40 / 100 · D | 66 / 100 · C |
|---|
| Reliability | 5 / 20 | 8 / 20 |
|---|
| Security and permissions | 6 / 20 | 15 / 20 |
|---|
| Maintenance | 7 / 20 | 15 / 20 |
|---|
| Documentation | 10 / 20 | 15 / 20 |
|---|
| Setup experience | 12 / 20 | 13 / 20 |
|---|
| Best for | - Users who need AI assistants to directly operate Todoist tasks.
- Developers who want seamless task management in AI tools like Claude, Cursor, VS Code.
- Developers who want to build custom AI workflows with reusable tools.
| - 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
|
|---|
| Not for | - Users who do not need AI task management features.
- Enterprises requiring multi-user collaboration or permission management (this server operates on a single user account).
- Users with strict data privacy requirements (third-party service may need evaluation).
| - 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
|
|---|
| Required permissions | - Requires a valid Todoist API key (TODOIST_API_KEY) or OAuth authentication.
- Tools can read and modify user's Todoist account data, including tasks, projects, and labels.
| - 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
|
|---|
| Risks and side effects | - AI agents may accidentally delete or modify tasks; it is recommended to use a test account or temporary project.
- Leaked API keys or OAuth tokens could lead to unauthorized account access.
- As it relies on external services, there is potential for downtime or latency.
| - 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
|
|---|
| Supported clients | Claude Desktop, Cursor, Claude Code, VS Code | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 5 | 0 |
|---|