trello-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRELLO_TOKEN | Yes | Trello API token | |
| TRELLO_API_KEY | Yes | Trello API key | |
| TRELLO_LIST_ID | No | Default list id | |
| TRELLO_BOARD_ID | No | Default board id |
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 |
|---|---|
| list_my_boardsA | List all boards the authenticated user belongs to. |
| get_boardB | Get a single board by its id. |
| create_boardB | Create a new board. |
| update_boardA | Update a board's name, description, or open/closed state. |
| delete_boardA | PERMANENTLY delete a board. This cannot be undone. Prefer update_board with closed=true to archive instead. |
| get_board_listsC | Get the lists on a board. |
| get_board_cardsC | Get the cards on a board. |
| get_board_labelsB | Get the labels defined on a board. |
| get_board_membersC | Get the members of a board. |
| create_listC | Create a new list on a board. |
| get_listB | Get a single list by its id. |
| update_listB | Update a list's name or position. |
| archive_listB | Archive (value=true) or unarchive (value=false) a list. Reversible. |
| get_list_cardsC | Get the cards in a list. |
| archive_all_cards_in_listB | Archive every card in a list. Reversible per-card. |
| create_cardC | Create a new card in a list. |
| get_cardA | Get a single card by its id. |
| update_cardA | Update a card. Use idList to MOVE the card to another list, closed=true to ARCHIVE it, due/dueComplete for due dates, and idAttachmentCover to set an existing image attachment as the card's cover. |
| delete_cardA | PERMANENTLY delete a card. This cannot be undone. Prefer update_card with closed=true to archive instead. |
| add_commentB | Add a comment to a card. |
| add_card_memberB | Assign a member to a card. |
| remove_card_memberB | Unassign a member from a card. |
| add_label_to_cardB | Attach an existing board label to a card. |
| remove_label_from_cardB | Detach a label from a card. |
| get_card_attachmentsC | List the attachments on a card. |
| add_attachmentA | Attach a URL to a card. Set setCover=true to make a publicly-fetchable image the card's cover (Trello must be able to preview the image). |
| delete_attachmentA | Remove an attachment from a card. |
| create_checklistB | Add a new checklist to a card. |
| add_checklist_itemC | Add a check item to a checklist. |
| update_checklist_itemA | Update a check item on a card: mark it complete/incomplete, rename it, or reposition it. |
| delete_checklistA | Delete a checklist from a card. |
| create_labelB | Create a new label on a board. |
| get_meB | Get the profile of the authenticated user. |
| get_memberA | Get a member by id or username. |
| searchC | Search cards, boards, and organizations. |
| search_membersC | Search for Trello members by name or username. |
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 36 tools
Each tool targets a distinct resource-action pair (e.g., board, list, card, checklist, label, member). Even similar operations like archive_list vs archive_all_cards_in_list are clearly differentiated by the resource they act on. Descriptions further clarify any ambiguity.
Most tools follow a verb_noun pattern (e.g., create_board, get_card). However, there is minor inconsistency between 'add' and 'create' (e.g., add_attachment vs create_board), but overall the pattern is consistent and predictable.
With 36 tools covering boards, lists, cards, checklists, labels, members, attachments, comments, and search, the count is well-proportioned for Trello's feature set. Each tool serves a clear purpose without feeling excessive.
The server covers CRUD for boards, lists, and cards, plus operations on checklists, labels, members, attachments, and comments. Minor gaps exist (e.g., no update label, no add board member), but core workflows are fully supported.