MCP Server Trello
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRELLO_TOKEN | Yes | Your Trello token (generate using your API key) | |
| TRELLO_API_KEY | Yes | Your Trello API key (get from https://trello.com/app-key) | |
| TRELLO_BOARD_ID | Yes | ID of the Trello board to interact with (found in board URL) |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_cards_by_list_idB | Fetch cards from a specific Trello list |
| get_listsB | Retrieve all lists from the specified board |
| get_recent_activityC | Fetch recent activity on the Trello board |
| add_card_to_listC | Add a new card to a specified list |
| update_card_detailsC | Update an existing card's details |
| archive_cardC | Send a card to the archive |
| add_list_to_boardC | Add a new list to the board |
| archive_listC | Send a list to the archive |
| get_my_cardsA | Fetch all cards assigned to the current user |
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 9 tools
Each tool has a clearly distinct purpose with no ambiguity: adding cards/lists, archiving cards/lists, fetching cards by list/board/user, getting activity, and updating cards. The descriptions reinforce this by specifying unique actions on different Trello entities.
The naming is mostly consistent with a verb_noun pattern (e.g., add_card_to_list, archive_card, get_cards_by_list_id), but there are minor deviations like 'get_my_cards' (which could be 'get_cards_by_user' for full consistency) and 'get_recent_activity' (which doesn't follow the verb_noun structure as tightly).
With 9 tools, this is well-scoped for a Trello server, covering core operations like CRUD for cards and lists, archiving, and activity tracking. Each tool earns its place without feeling excessive or insufficient for managing Trello boards.
The toolset provides strong coverage for Trello's domain, including create (add_card_to_list, add_list_to_board), read (get_cards_by_list_id, get_lists, get_my_cards, get_recent_activity), update (update_card_details), and delete/archive (archive_card, archive_list). A minor gap is the lack of a tool to update list details, but agents can work around this.