Trello MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TRELLO_TOKEN | Yes | Trello access token generated from Trello Developer Portal | |
| TRELLO_API_KEY | Yes | Trello API Key obtained from Trello Developer Portal |
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 |
|---|---|
| tre__get_boardsB | Get all boards for the authenticated user |
| tre__get_listsB | Get all lists in a board |
| tre__get_cardsC | Get all cards in a list |
| tre__create_cardC | Create a new card in a list |
| tre__update_cardC | Update an existing card |
| tre__delete_cardC | Delete a card |
| tre__invite_to_boardC | Invite a member to a board by email |
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 7 tools
Each tool has a clearly distinct purpose targeting specific Trello resources and actions, with no overlap in functionality. For example, get_boards, get_lists, and get_cards handle different retrieval operations, while create_card, update_card, and delete_card manage the card lifecycle distinctly.
All tools follow a consistent verb_noun pattern with the 'tre__' prefix, using clear action verbs like create, delete, get, invite, and update. The naming is uniform and predictable across all seven tools, making them easily distinguishable and readable.
With 7 tools, this server is well-scoped for managing Trello boards, lists, cards, and members. Each tool serves a specific purpose without redundancy, covering core operations like retrieval, creation, updates, and invitations in a concise and effective manner.
The tool set provides solid CRUD coverage for cards and basic board/list management, with minor gaps such as missing operations for updating or deleting boards/lists, and no tools for handling comments or attachments on cards. However, the core workflows for card lifecycle and board access are adequately covered.