F
licenseNot graded
qualityD
maintenanceThis is an MCP Server for Trello that enables interaction with Trello's API through natural language, allowing management of boards, cards, lists, and other Trello resources.
-
Trello MCP Server
by stucchi
Related Servers
Alternatives to Trello MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for Trello that enables comprehensive management of boards, cards, lists, labels, checklists, attachments, members, custom fields, and search through natural language.101 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for Trello integration, enabling management of workspaces, boards, lists, cards, and checklists through natural language.MIT
- FlicenseAqualityDmaintenanceA powerful MCP server for interacting with Trello boards, lists, and cards via AI Hosts.2254-
- AlicenseBqualityCmaintenanceAn MCP server for the Trello REST API. Exposes ~36 curated tools for boards, lists, cards, checklists, labels, members, and search.366 npmMIT
- AlicenseNot gradedqualityCmaintenanceMCP server that integrates Trello with AI agents, enabling natural language management of boards, lists, cards, checklists, attachments, and custom fields.234 npm2MIT
TDQS
B3.1/5.0
Scored across 28 tools
Disambiguation5/5
Each tool has a clear, distinct purpose targeting a specific Trello resource and action. No two tools overlap in functionality; e.g., add_card_attachment and add_card_url_attachment are differentiated by file vs URL attachment.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern (e.g., create_board, get_card, add_checklist_item). The naming convention is uniform and predictable.
Tool Count4/5
28 tools is on the higher side but still reasonable for a comprehensive Trello server covering boards, lists, cards, checklists, labels, attachments, comments, and history. It is slightly above the 'heavy' threshold but not excessive given the domain complexity.
Completeness2/5
Significant gaps exist: missing delete_card (only archive), delete/update for lists, update/delete for checklists, update/delete for labels, and update_board. These absences will likely cause agent failures in common workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues