Trello MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRELLO_TOKEN | Yes | Your Trello access token | |
| TRELLO_API_KEY | Yes | Your Trello API 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_boardsB | Get all boards for the authenticated user |
| get_listsC | Get all lists in a board |
| get_cardsC | Get cards from a board or specific list |
| get_card_detailsC | Get detailed information about a specific card |
| update_cardC | Update properties of a specific 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 5 tools
Each tool has a clearly distinct purpose targeting specific Trello resources: get_boards (boards), get_lists (lists), get_cards (cards in board/list), get_card_details (specific card details), and update_card (modify card). No ambiguity or overlap exists between these operations.
All tools follow a consistent verb_noun pattern with snake_case: get_boards, get_card_details, get_cards, get_lists, update_card. The naming is predictable and readable throughout the set.
Five tools is reasonable for a Trello server, covering core read operations and one update. It's slightly under-scoped as it lacks create/delete operations for boards, lists, or cards, but the count itself is appropriate for the provided functionality.
The toolset covers read operations well (boards, lists, cards, card details) and one update (card), but there are notable gaps: no create or delete tools for any resources (boards, lists, cards), and missing operations like moving cards between lists or managing members. This limits full lifecycle management.