trello-ops-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level: debug, info, warn, or error. Defaults to info. | info |
| TRELLO_TOKEN | Yes | Your Trello read-only token generated from https://trello.com/app-key | |
| TRELLO_API_KEY | Yes | Your Trello API key from https://trello.com/app-key |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Checks that the trello-ops-mcp server is running and reachable. Requires no Trello credentials — useful for verifying the MCP connection itself before troubleshooting anything else. |
| get_boardsA | Get the Trello boards accessible to the configured account. |
| get_board_listsA | Get the lists on a Trello board, identified by ID, shortLink, or board URL. |
| get_board_membersA | Get the members on a Trello board, identified by ID, shortLink, or board URL. |
| get_board_cardsA | Get the cards on a Trello board, identified by ID, shortLink, or board URL. Returns raw card data (list, members, due date) — no overdue/analytics computation. |
| get_board_actionsA | Low-level historical inspection/debug tool: returns a compact, normalized view of a board's raw action history. For structural list-change auditing, prefer get_list_changes. |
| get_list_changesA | Main structural audit tool: who created, renamed, archived, or unarchived lists on a board, optionally scoped to a date range and/or a single list. |
| get_card_movementsA | List confirmed list-to-list card movements from a board's action history, optionally filtered by member, card, source list, or destination list. Workflow activity, not a productivity metric. |
| get_top_card_moversA | Ranks board members by list-to-list card movements in a date range (explicit since/before, or the convenience |
| get_member_activityA | Normalized chronological activity feed for one board member: card movements, list structural changes, card creation, and card archival. Resolve by memberId when known; memberName is looked up against board members and rejected with a clear error if it's ambiguous or matches no one. |
| get_overdue_cardsA | Cards with a past-due date that aren't marked complete and aren't archived, based on the board's current card state (not action history). Sorted most-overdue first. |
| get_upcoming_due_cardsA | Cards due within the next N days (default 7) that aren't marked complete and aren't archived, based on the board's current card state (not action history). Sorted soonest-due first. |
| get_list_flowA | Returns incoming and outgoing card movement counts by Trello list for a date range (explicit since/before, or the convenience |
| get_stale_cardsA | Returns open cards with no recognized activity (creation, list move, archive/unarchive) for at least |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.