Trello MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRELLO_LANG | No | Forced message language: en, ru, or uk. | |
| TRELLO_TOKEN | No | Trello token. Takes priority over the config file. | |
| TRELLO_API_KEY | No | Trello API key. Takes priority over the config file. | |
| TRELLO_AUTH_MODE | No | Authentication mode: auto or manual. | |
| TRELLO_AUTH_PORT | No | Port for the local token receiver. Defaults to 8765. | 8765 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
Always reply to the user in the language they write in (if you cannot tell, use the system language, otherwise English). Pass that language as the optional lang argument (ISO 639-1, e.g. en, ru, uk) on every tool call so that the server's own messages (connection instructions, progress log, browser page) come back in the same language. If Trello is not connected, ask the user whether they prefer automatic or manual connection, then call trello_connect.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| trello_statusA | Show Trello connection status: whether the API key and token are set, the auth mode, and the recent connection log. |
| trello_connectA | Connect to Trello. mode=auto: opens the browser, the user clicks Allow, the token is captured and saved automatically. mode=manual: without |
| list_boardsC | List the boards of the current Trello user. |
| get_boardC | Get a board's details. |
| create_boardC | Create a new board. |
| get_listsC | Get the lists on a board. |
| create_listC | Create a list on a board. |
| archive_listB | Archive (close) a list. |
| get_cardsA | Get the cards in a list, or on a board (provide exactly one of listId/boardId). Returns an array. For big boards paginate with |
| get_cardB | Get a card's full details, including checklists and members. |
| create_cardC | Create a card in a list. |
| update_cardA | Update a card: rename, change description/due/start date, move to another list (and, with boardId, to another board), or archive. |
| delete_cardA | Permanently delete a card. This cannot be undone; prefer update_card with closed=true. |
| add_commentC | Add a comment to a card. |
| searchC | Search Trello for cards and boards. |
| get_labelsC | Get the labels defined on a board. |
| create_checklistC | Add a checklist to a card, optionally with items. |
| update_boardB | Rename a board, change its description, or close (archive) / reopen it. |
| delete_boardA | PERMANENTLY delete a board with all its lists and cards. Cannot be undone; prefer update_board with closed=true. |
| get_board_membersA | List the members of a board (ids are needed for assign_member). |
| update_listA | Rename a list, change its position (top, bottom, or a number), or archive/unarchive it. |
| create_labelC | Create a label on a board. |
| add_labelC | Attach an existing label to a card. |
| remove_labelA | Detach a label from a card (the label itself stays on the board). |
| add_checklist_itemC | Add an item to an existing checklist. |
| set_checkitem_stateC | Mark a checklist item complete or incomplete. |
| delete_checklistB | Delete a checklist from a card. Cannot be undone. |
| add_attachmentB | Attach a URL (link) to a card. |
| get_commentsA | Get the comments on a card, newest first. Page with |
| assign_memberB | Assign a board member to a card (get ids from get_board_members). |
| copy_cardB | Copy a card (with checklists, labels, attachments, comments, members) into a list, possibly on another board. |
| copy_listB | Copy a list with all its cards onto a board (the same or another one). |
| copy_boardB | Copy a board. With includeCards=true (default) the cards are copied too. |
| invite_memberA | Invite a person to a board by email. SIDE EFFECT: Trello sends an invitation email to that address, so only call this when the user explicitly asked for this exact invitation. |
| remove_member_from_boardB | Remove a member from a board (they lose access to it). |
| unassign_memberA | Remove a member from a card (they stay on the board). |
| set_coverA | Set a card's cover: a colour, an existing attachment as an image, or remove the cover (remove=true). |
| get_custom_fieldsA | List the custom fields defined on a board (empty if the Custom Fields Power-Up is not enabled). |
| create_custom_fieldA | Create a custom field on a board (enables the Custom Fields Power-Up first if needed). For type=list pass |
| set_custom_fieldA | Set a custom field value on a card. |
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 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.