Trello Task Manager MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| add_taskC | Create a Trello card in the configured To Do list. |
| list_tasksA | List active cards from the configured To Do list. |
| complete_taskC | Move a Trello card into the configured Done list. |
| delete_taskC | Archive a Trello card and return its details. |
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 4 tools
Each tool targets a distinct action on Trello cards: add, list, complete, and delete. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern (complete_task, delete_task, add_task, list_tasks), making them predictable.
With 4 tools, the server is well-scoped for a basic task manager, covering essential operations without unnecessary bloat.
The server lacks an update tool for modifying card details (e.g., description, due dates) and a get-single-card tool, which are notable gaps for a task manager.