Trello MCP
Related Servers
Alternatives to Trello MCP
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables AI assistants to manage Trello boards, lists, cards, comments, checklists, labels, and members through natural language.16-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage Trello boards, lists, cards, labels, checklists, members, comments, and attachments through natural language.96 npmISC
- AlicenseNot gradedqualityCmaintenanceEnables reading, creating, updating, and managing Trello boards, lists, cards, members, and labels via natural language.309 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables interaction with Trello boards, lists, and cards through the Trello REST API. Supports board management, card operations, member management, labels, and checklists through natural language.1MIT
- AlicenseNot gradedqualityCmaintenanceEnables managing Trello boards, lists, cards, labels, and members through natural language from any MCP-compatible client.1MIT
- AlicenseBqualityDmaintenanceConnects Trello with AI assistants to manage boards, lists, cards, and comments via natural language.117MIT
TDQS
Scored across 40 tools
Most tools target a clearly distinct resource+action (get_card vs create_card vs copy_card vs delete_card, add_label vs remove_label, assign_member vs unassign_member). A few boundaries blur: archive_list overlaps with update_list's archive/unarchive, and delete_board/delete_card duplicate the close-flag behavior of update_board/update_card, though descriptions steer users to the safer option.
Predominantly a verb_noun pattern (get_board, create_card, add_comment, copy_list, set_custom_field) with snake_case throughout. Minor deviations: the prefixed auth tools trello_status/trello_connect, the bare verb 'search', and inconsistent 'checkitem' vs 'checklist_item' naming.
40 tools is heavy for an MCP surface and exceeds the threshold where an agent can hold the catalog comfortably in context. While Trello is a broad domain, several tools (auth, copy variants, separate archive/delete paths) inflate the set beyond what is strictly needed.
Core lifecycle for boards, lists, cards, labels, members, checklists, comments and custom fields is covered. However, sub-resources have add/set operations without their counterparts: no delete/update checklist item, no update/delete label, no remove attachment, no edit/delete comment, and no delete custom field — forcing dead ends.