Trellis
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port for the HTTP server. Used when running in hosted mode (e.g., `PORT=8080 .venv/Scripts/python -m trellis.smithery_app`). | |
| TRELLO_TOKEN | Yes | Trello token tied to your Trello account, granting access to your boards. | |
| TRELLO_API_KEY | Yes | Trello API key obtained from https://trello.com/power-ups/admin |
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 |
|---|---|
| list_boardsA | List every Trello board the authenticated account can open. Returns board ids, names and URLs. This is the entry point for every other tool, which all need a board id or name. |
| get_board_infoA | Get metadata for one board: name, description, URL, visibility, last activity.
|
| list_board_listsA | List the open lists (columns) on a board, in board order, with card counts. |
| list_cardsA | List open cards on a board, optionally filtered to one list by name. Each card is trimmed to a triage digest: labels, assignee count, due date, overdue flag, days idle, and checklist progress. |
| get_cardA | Get one card in full: description, labels, due date, checklists and recent comments. |
| search_trelloA | Search cards and boards across the whole account using Trello's own search. Supports Trello search operators such as |
| analyze_board_healthB | Assess a board: per-list load, overdue cards, unassigned work and stalled cards. Returns counts and the specific offending cards, not a verdict. Read the numbers and say what they imply, including when the board is simply small. |
| detect_bottlenecksA | Rank the non-done lists by how much work is piling up and ageing inside them. The pressure score is a crude volume-plus-age heuristic and is returned with its own formula so it can be argued with rather than trusted blindly. |
| generate_standup_reportA | Summarise what actually happened on a board recently. Combines card movements, new cards and comments from the activity feed with the board's current overdue and stalled work, which is enough material for a standup update or a weekly status note. |
| create_cardA | Create a card on a board, in the named list. This writes to the real board.
|
| move_cardA | Move a card to a different list on the same board. This writes to the real board.
|
| update_cardA | Update a card's name, description, due date, or archive it. This writes to the real board. Only the arguments you pass are changed. |
| add_commentA | Post a comment on a card as the authenticated user. This writes to the real board. |
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 13 tools
Most tools target distinctly different resources and actions: boards, lists, cards, search, and write operations are clearly separated. The only mild overlap is between analyze_board_health and detect_bottlenecks, both assessing board workflow strain, but their descriptions clarify one is overall health and the other is list pressure ranking.
Every tool follows a lowercase verb_noun pattern: list_boards, get_card, create_card, move_card, add_comment, and so on. Even the more analytical tools like analyze_board_health and detect_bottlenecks fit the same predictable style.
Thirteen tools is within the ideal 3–15 range and every tool earns its place in a Trello-focused server. The set balances read, write, search, and analysis tools without padding or redundant duplication.
The toolset covers core workflows well: board discovery, list and card inspection, card creation/update/move/comment, archiving via update, search, and higher-level workflow analysis. Missing board/list creation and card deletion are minor gaps for a board-management assistant and can be worked around.