Trello MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Optional: Port for HTTP transport | |
| DEBUG | No | Optional: Enable debug logging | |
| TRELLO_API_KEY | Yes | Your Trello API Key from the Trello Developer Portal | |
| TRELLO_API_TOKEN | Yes | Your Trello API Token generated from the 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| boards |
TDQS
Scored across 16 tools
Multiple tools have unclear boundaries due to singular/plural pairs that create ambiguity. For example, 'add-comment' and 'add-comments' appear to do the same thing but with different scales, which could cause misselection. Similarly, 'archive-card' vs 'archive-cards' and 'create-card' vs 'create-cards' create confusion about when to use which tool.
Tool names follow a consistent kebab-case pattern with verb-noun structure throughout, such as 'add-comment', 'create-card', and 'get-boards'. The main deviation is the inconsistent handling of singular vs plural nouns, but the overall naming convention is predictable and readable.
With 16 tools, the count is slightly high but reasonable for a Trello server covering boards, cards, lists, labels, and comments. It includes core operations like create, get, move, and archive, though some tools might be redundant due to singular/plural pairs.
The tool set covers basic CRUD operations for cards, labels, and comments, but has notable gaps. For example, there are no tools for updating or deleting cards, lists, or labels, and no way to retrieve individual cards or boards by ID. This could cause agent failures in common workflows like editing card details.