| FMRS | 47 / 100 · D | 66 / 100 · C |
|---|
| Reliability | 6 / 20 | 8 / 20 |
|---|
| Security and permissions | 8 / 20 | 15 / 20 |
|---|
| Maintenance | 7 / 20 | 15 / 20 |
|---|
| Documentation | 14 / 20 | 15 / 20 |
|---|
| Setup experience | 12 / 20 | 13 / 20 |
|---|
| Best for | - Individuals or teams already using Trello for task management who want to manipulate cards and lists conversationally via Claude Desktop or Cursor
- Developers who want quick Trello access from Claude Desktop or any SSE-capable MCP client
| - 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 need to create, rename, or delete entire boards (not supported)
- Users without a Trello API Key/Token or without access to the Trello Power-Up admin page
- Scenarios requiring official Trello/Atlassian support or enterprise-grade security auditing
| - 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 | - A Trello API Key and Token (account-level access to read/write boards, lists, cards, and checklists the account can access)
- Local .env file storing credentials in plaintext
- Network access to call the Trello API, and (in SSE mode) an open local HTTP port
| - 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 | - API Key and Token are stored in plaintext in the .env file — leakage grants full control over the Trello account
- Delete/archive operations on lists, cards, checklists, and checklist items are irreversible
- SSE mode exposes a local HTTP endpoint; the README does not mention any built-in authentication for it
- This is a community-maintained third-party server, not reviewed or endorsed by Trello/Atlassian
| - 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 | OpenAI ChatGPT, Claude, Cursor, GitHub Copilot, GitHub Copilot CLI, Google Gemini CLI, Amazon Quick Suite, Local MCP-compatible clients via mcp-remote |
|---|
| Tools | 0 | 0 |
|---|