Trello
The Trello connector allows AI agents to browse boards, manage cards, and add comments via the Trello REST API using Atlassian OAuth 2.0. Your credentials are stored encrypted in MCPGate's vault and are never exposed to the AI client.
Archive is not permanent delete
trello_archive_cardarchives the card — it does not permanently delete it. Archived cards can be restored from the board's archived items view in Trello.Tool reference#
The Trello connector exposes 7 tools: 3 read, 3 write, and 1 delete.
| Tool | Category | Description |
|---|---|---|
| trello_list_boards | read | List user's Trello boards |
| trello_get_board | read | Get board details with lists |
| trello_list_cards | read | List cards on a board or list |
| trello_create_card | write | Create a new card |
| trello_update_card | write | Update card (move, rename, etc.) |
| trello_add_comment | write | Add comment to a card |
| trello_archive_card | delete | Archive a card |
Common guardrail recipes#
Read-only access#
Enable only trello_list_boards, trello_get_board, and trello_list_cards. Deny all write and delete tools. Useful for project status reporting agents that should only observe the board.
Restrict to specific boards#
Apply the allow_values template to trello_create_card and trello_update_card, targeting the board_id field. The AI will only be permitted to create or update cards on the boards you specify.
Comment-only write access#
Enable only trello_add_comment from the write tools while denying trello_create_card, trello_update_card, and trello_archive_card. This allows the AI to annotate cards without modifying them.
Troubleshooting#
- Board not visible — Trello boards must be accessible to the authenticated account. Private boards owned by other workspace members will not appear in
trello_list_boards. - Card move fails —
trello_update_cardmoves a card by specifying alist_id. The target list must exist on the same or a different board that the account can access. - OAuth scope error— Trello's Atlassian OAuth requires explicit read and write scopes. Reconnect the connector if you receive a scope-related error.