trello-ops-mcp
Related Servers
Alternatives to trello-ops-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceThis read-only MCP server enables users to query Trello data, including boards, lists, cards, checklists, and board activity, through the Trello REST API.-
- AlicenseAqualityDmaintenanceMCP server that provides read and write access to Trello boards, enabling AI assistants to list, search, create, update, move, comment, label, and archive cards via natural language.15MIT
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides AI assistants with access to Trello's functionality. This server enables AI models to interact with Trello boards, lists, and cards programmatically.1MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that integrates Trello with AI agents, enabling natural language management of boards, lists, cards, checklists, attachments, and custom fields.2MIT
- AlicenseNot gradedqualityCmaintenanceMCP server that provides a real-time project management board with cards, sprints, comments, and docs, enabling coding agents to query and edit project state.2MIT
- AlicenseBqualityDmaintenanceAn MCP server for the Trello REST API. Exposes ~36 curated tools for boards, lists, cards, checklists, labels, members, and search.368 npmMIT
TDQS
Scored across 14 tools
Most tools target a distinct resource and concern (boards, lists, members, cards, actions). The main overlap is between get_board_actions, get_list_changes, get_card_movements, and get_member_activity, but the descriptions explicitly differentiate raw history from normalized/audit views and direct users to the intended tool.
All tools follow a consistent get_* pattern with descriptive noun phrases (e.g., get_board_lists, get_list_changes, get_top_card_movers). There is no mixing of styles or vague verbs, making the set predictable.
With 14 tools, the set is well-scoped for a Trello operations/monitoring server. Each tool addresses a specific query need without redundancy, and the count sits comfortably within the ideal range.
The server covers the core read/monitoring surface for Trello boards: lists, members, cards, activity, and action history. The only notable gap is a single-card detail endpoint, but get_board_cards already provides raw card data, so agents can work around this minor omission.