The tool set matches how a board is actually used — moving a card between lists, ticking a checklist item, putting a label on something — rather than stopping at read. That means the token you generate has `read,write,account` scope and the agent can delete cards, so use it on a board you can afford to have edited.
A TypeScript server over the Trello REST API, authenticated with your own key and token. It covers the objects a board is made of rather than one slice of them.
- Boards listed and inspected, with their members — `list_boards`, `get_board`, `get_board_members`
- Lists read, created, renamed and repositioned — `get_lists`, `create_list`, `update_list`
- Cards read, created, edited, moved between lists and deleted — `get_cards`, `create_card`, `update_card`, `move_card`, `delete_card`
- Members added to and removed from a card — `add_card_member`, `remove_card_member`
- Labels listed for a board, then applied to or removed from a card — `get_labels`, `add_card_label`, `remove_card_label`
- Checklists read and created on a card, with items added and marked complete — `get_card_checklists`, `create_checklist`, `add_checklist_item`, `update_checklist_item`
A Trello account with API access: take your key from trello.com/app-key and generate a token with `read,write,account` scope, then set `TRELLO_API_KEY` and `TRELLO_TOKEN`. Node.js 18+ and npm; `npm install`, `npm run build`, and point the client at `dist/index.js`. There is also a Docker path, including Docker Desktop's built-in MCP support from version 4.38 onward.
Run a container — pull the image and point your client at it