A Trello MCP that knows the difference between archive and delete
Connect a Trello API key and member token and boards, lists, cards, checklists, labels, comments, and webhooks become workflow steps for visual automations and AI agents. The connector keeps Trello's distinctions honest: closing a board and archiving a card or list are reversible and ship as their own nodes, while the eight permanent delete nodes are flagged so you can gate them.
What the Trello MCP connector does
The Trello connector for Mattering Automations is 45 nodes across Trello's REST API: boards (list, get, create, update, close and reopen, delete), lists, cards (list, get, create, update, move, archive, delete), checklists and check items, labels, board members and card assignment, comments, URL attachments, webhook management, and Trello's cross-board search. The split is 15 query nodes and 30 action nodes.
Every node speaks MCP, the open protocol for connecting AI assistants to tools, so Claude, ChatGPT, and any MCP-capable assistant can use them, alongside Matter, the AI assistant built into the platform. An assistant can answer which cards are stuck in a column, who is assigned where, and what is overdue across boards, without anyone opening Trello.
Because Mattering is a work platform rather than middleware, Trello work lands somewhere useful by default: a scheduled sweep of a Done column can close matching tasks in Mattering Productivity, a form submission can become a Trello card with a record in a Mattering database beside it, and Trello events, delivered through a webhook whose callback points at an inbound trigger, can fan out to the rest of the canvas.
The connector is honest about what can be undone. Closing a board and archiving a card or list are reversible, and each ships as its own node. The eight delete nodes are flagged destructive because Trello deletes are permanent: there is no trash, and a deleted board or card cannot be recovered. Lists are the one thing Trello cannot delete at all; archiving is their terminal state, and it is fully reversible.
One connection, three surfaces
- Visual automations. Drag Trello nodes onto the canvas and wire them to triggers, conditions, and other apps.
- AI agents, yours or ours. These nodes speak MCP, the open protocol, so Claude, ChatGPT, and any MCP-capable assistant can use them, and Matter, the agent built into the platform, uses them natively.
- The whole platform. Combine with native tasks, projects, and other connectors, no middleware in between.
Every Trello node, ready to drop on the canvas
45 nodes, generated from the connector itself so this list always matches what ships. Expand a category to browse.
Read and query nodes 15
Trello: Get Board
Get a single board with its name, description, closed state, preferences, and label names. Optional nested resources pull the board's lists, cards, labels, and members in one call.
Trello: Get Card
Get a single card with its name, description, due date, labels, and badges. Optional nested resources pull the card's attachments, members, checklists, and comment actions in the same call.
Trello: Get List
Get a single list: name, position, closed state, and the id of the board it belongs to.
Trello: Get My Member
Get the authenticated Trello member: id, username, full name, and the ids of their boards and Workspaces. Needs no configuration, so it doubles as the credential health check (401 when the key or token is wrong).
Trello: List Board Members
List the members of a board with their ids, usernames, and full names. The returned member ids feed card assignment.
Trello: List Card Attachments
List a card's attachments: name, URL, whether it was an upload or a link, and the attachment id used by Delete Attachment.
Trello: List Card Comments
List a card's comments (commentCard actions), newest first. Each entry carries the comment text under data.text plus the commenting member; the action id feeds Delete Comment.
Trello: List Cards in List
List the cards in a single list (column), in board order. The classic polling read for column-driven automations.
Trello: List Cards on Board
List the open cards on a board across all of its lists. For one column only, use Trello: List Cards in List instead.
Trello: List Checklists on Card
List a card's checklists with their check items and states. The returned checklist and check item ids feed the check item nodes.
Trello: List Labels on Board
List a board's labels with their names and colors. The returned label ids feed card labeling and label updates.
Trello: List Lists on Board
List the lists (columns) on a board, open ones by default. Optionally include each list's cards inline. The returned list ids feed card creation and moves.
Trello: List My Boards
List the boards the authenticated member belongs to. Filter by open, closed, starred, or organization membership. The returned board ids feed every board-scoped node.
Trello: List Webhooks
List every webhook registered on this connector's token, with each webhook's model, callback URL, active flag, and failure count. The token in the path is filled in by the connector from the stored credential; it is never part of the node's configuration or output.
Trello: Search
Search across the member's cards, boards, members, and Workspaces with Trello's search operators (board:, list:, label:, due:, @member, and friends). Results come back grouped by model type.
Action nodes 30
Trello: Add Check Item
Add an item to a checklist, optionally already checked, with a due date or an assigned member (due dates and assignees on check items are a Trello Premium feature). Returns the created check item.
Trello: Add Comment to Card
Post a comment on a card as the token's member. Returns the created commentCard action; its id is what Delete Comment takes.
Trello: Add Label to Card
Add one existing label to a card without touching the card's other labels. Removing it again restores the exact previous state.
Trello: Add Member to Card
Assign one board member to a card without touching the card's other members. Removing them again restores the previous state.
Trello: Archive / Unarchive Card
Archive a card, or send it back to the board with closed=false. Archived cards keep all their content and are recoverable from the board's archive; this is the reversible alternative to the destructive Delete Card node.
Trello: Archive / Unarchive List
Archive a list, or restore it with value=false. Archiving hides the list (and its cards) from the board without deleting anything; Trello has no list delete at all, so archive is the terminal state and it is fully reversible.
Trello: Attach URL to Card
Attach a link to a card by URL. This connector attaches by URL only (Trello stores the link, isUpload stays false); the API's multipart file upload is deliberately not exposed because the canvas cannot produce file bytes.
Trello: Close / Reopen Board
Close (archive) a board, or reopen it with closed=false. A closed board disappears from the boards page but keeps all lists and cards and can be reopened at any time. This is the reversible alternative to the destructive Delete Board node.
Trello: Create Board
Create a new board. By default Trello seeds it with the To Do, Doing, and Done lists; turn that off with defaultLists=false to start empty. Returns the created board with its id.
Trello: Create Card
Create a card in a list, with optional description, due and start dates, members, labels, and a source URL that becomes the card's first attachment. Returns the created card with its id and shortUrl.
Trello: Create Checklist
Add a checklist to a card, optionally copying the items of an existing checklist with idChecklistSource. Returns the created checklist with its id.
Trello: Create Label
Create a new label on a board with a name and one of Trello's named colors. Returns the created label with its id.
Trello: Create List
Create a new list (column) on a board. Optionally copy an existing list's cards with idListSource. Returns the created list with its id.
Trello: Create Webhook
Register a webhook: Trello will POST every action on the watched model (a board, list, or card id) to your callback URL. MANAGEMENT ONLY: this does not create an Automations trigger by itself; point callbackURL at an Automations inbound webhook trigger URL to receive the events. At creation Trello sends an HTTP HEAD request to the callback and requires a 200 response, or the webhook is not created. Failed deliveries are retried 3 times; a callback answering 410 deletes the webhook.
Trello: Delete Attachment
DESTRUCTIVE: delete an attachment from a card. A link attachment could be re-added, but a FILE that was uploaded to Trello is permanently gone, so the node is flagged for the worst case it can hit.
Trello: Delete Board
DESTRUCTIVE: permanently delete a board and every list and card on it. There is no undo and no trash; a deleted board cannot be recovered by Trello support either. If the board might be needed again, use Close / Reopen Board instead.
Trello: Delete Card
DESTRUCTIVE: permanently delete a card with its comments, checklists, and attachments. There is no undo. If the card might be needed again, use Archive / Unarchive Card instead.
Trello: Delete Check Item
DESTRUCTIVE: delete a single check item from a checklist. There is no undo; to keep the item but clear it, use Update Check Item with state=incomplete instead.
Trello: Delete Checklist
DESTRUCTIVE: delete a checklist and every check item on it. There is no undo and no archive state for checklists.
Trello: Delete Comment
DESTRUCTIVE: delete a comment from a card. Only comment actions can be deleted, only by their author or a board admin, and there is no undo.
Trello: Delete Label
DESTRUCTIVE: delete a label from its board, stripping it from every card that carries it. There is no undo; to take it off one card only, use Remove Label from Card.
Trello: Delete Webhook
DESTRUCTIVE: delete a webhook subscription. Delivery stops immediately and the deletion cannot be undone; an equivalent webhook can be recreated with Create Webhook, but it arrives as a new object and events during the gap are lost.
Trello: Move Card
Move a card to another list (and optionally another board), with an optional position in the destination. The ergonomic shortcut for the most common Trello automation step; moving it back reverses it exactly.
Trello: Remove Label from Card
Take one label off a card. The label itself survives on the board and can be re-added, so this is a reversible write, unlike Delete Label.
Trello: Remove Member from Card
Unassign a member from a card. The member keeps their board access and can be re-added, so this is a reversible write.
Trello: Update Board
Update a board's name, description, closed state, Workspace, or subscription. Preference fields (prefs/{name}) go through extra_query. Returns the updated board.
Trello: Update Card
Update any card fields: rename, edit the description, change dates, replace the member or label sets (idMembers and idLabels REPLACE the existing sets), archive with closed, or relocate with idList/idBoard/pos. Returns the updated card.
Trello: Update Check Item
Update a check item, most importantly its state (complete or incomplete): this is the check/uncheck node. Trello scopes the update to the CARD, so both the card id and the check item id are required.
Trello: Update Label
Rename a label or change its color. The change applies everywhere the label is used on the board.
Trello: Update List
Rename or reposition a list, move it to another board with idBoard, or change the acting member's subscription. Returns the updated list.
Connecting Trello takes one credential
Trello issues both values from its Power-Up admin console at trello.com/power-ups/admin. A Power-Up, even an empty one created just for this, provides the API key, and the Token link beside the key authorizes a member token. The token acts as that member with the read and write access granted at authorization; Trello has no finer scopes, so treat the token like a password.
At trello.com/power-ups/admin, create a new Power-Up or open an existing one, and copy its API key.
Click the Token link shown beside the API key, review the access being granted, authorize it, and copy the member token.
In Mattering Automations, open Connectors, click Add Connector, choose Trello, and create a credential with the API key as the username and the token as the password. Click Test Connection: Mattering fetches your Trello member profile and reports the connected member by name.
All 45 Trello nodes appear in the canvas palette. Run Trello: List My Boards first: the board ids it returns feed every board-scoped node.
Common uses for the Trello MCP
Board questions an agent can answer
Trello: List My Boards, Trello: Get Board, and Trello: Search cover which boards exist, what is on them, and where a card lives, with Trello's search operators available for precise questions. Trello: Get Board and Trello: Get Card can pull nested lists, cards, members, checklists, and comments in one call, so an assistant can brief a whole board without a dozen round trips.
Column-driven workflows
Trello: List Cards in List is the classic polling read: run it on a schedule, compare against what a Mattering database already knows, and act on what changed. Trello: Move Card is the matching write and the single most common Trello automation step, and moving a card back reverses it exactly.
Cards created from anywhere
Trello: Create Card turns a form submission, a new record, or an assistant's request into a card with a description, due and start dates, members, and labels set in one step. Trello: Add Comment to Card carries the context, and Trello: Attach URL to Card links the card back to the record it came from.
Checklists as machine-readable progress
Trello: Create Checklist and Trello: Add Check Item let workflows build checklists, Trello: Update Check Item is the check and uncheck node, and Trello: List Checklists on Card reads the states back so a workflow can tell when everything on a card is actually done.
Labels and assignment without clobbering
Trello: Add Label to Card and Trello: Add Member to Card change exactly one thing and are exactly reversible with their remove counterparts. That matters because the idLabels and idMembers fields on Trello: Update Card replace the whole set; the incremental nodes exist so an automation never wipes a card's other labels or members by accident.
Trello events into the canvas
Trello: Create Webhook, Trello: List Webhooks, and Trello: Delete Webhook manage webhook subscriptions on a board, list, or card. They are management nodes rather than triggers, but the recipe is simple: point the callback URL at a Mattering Automations inbound webhook trigger and every action on the watched model arrives as an event a workflow can react to.
Example: A form submission becomes a Trello card, and the card's progress reports back
Built on the Automations canvas in a few minutes, or described in plain language to Matter and built for you.
Trigger: a form submission or a new record in a Mattering database supplies a title, a description, and a link to the source.
Trello: List Lists on Board finds the intake column's list id on the team board.
Trello: Create Card creates the card in that list with the description, a due date, and a label, and returns the card id and short URL.
Trello: Attach URL to Card links the card back to the originating record, and Trello: Add Comment to Card posts the context the team needs.
Trello: Create Webhook watches the board, with its callback pointed at a Mattering Automations inbound webhook trigger.
When the card moves to Done, the webhook event fires a second workflow that closes the matching task in Mattering Productivity and updates the record in the Mattering database.
Trello MCP questions, answered
What Trello operations are supported?
45 nodes across Trello's REST API: boards (list, get, create, update, close and reopen, delete), lists (list, get, create, update, archive), cards (list by board or list, get, create, update, move, archive, delete), checklists and check items, labels, board members and card assignment, comments, URL attachments, webhook management (list, create, delete), and cross-board search. Deliberately not shipped: file uploads (attachments are by URL only), board member invites, webhook updates (delete and recreate covers reconfiguration), and custom fields, which are the likeliest future addition if customers ask.
Does this work with Claude, ChatGPT, or other AI assistants?
Yes. Mattering exposes these nodes over MCP, an open protocol for connecting AI assistants to tools, so any MCP-capable assistant, including Claude and ChatGPT, can connect to your workspace and use them. Matter, the assistant built into the platform, uses the same nodes natively.
Can this connector destroy data?
Only through eight clearly flagged delete nodes, and each is honest about the stakes. Trello deletes are permanent, with no trash and no recovery: Trello: Delete Board takes every list and card with it, and Trello: Delete Card takes the card's comments, checklists, and attachments. Every delete node names the reversible alternative where one exists: Trello: Close / Reopen Board and Trello: Archive / Unarchive Card preserve everything and can be undone at any time. Gate the delete nodes behind a condition, an approval step, or a manual run.
Why is there no Delete List node?
Because Trello has no such endpoint: lists cannot be deleted, by this connector or by anything else. Trello: Archive / Unarchive List is the terminal state; it hides the list and its cards from the board without destroying anything, and it is fully reversible.
Can a Trello event trigger a workflow?
Yes, with one honest step in between. The webhook nodes manage Trello webhook subscriptions rather than acting as triggers themselves. Create a Mattering Automations inbound webhook trigger, then pass its URL as the callback in Trello: Create Webhook, and Trello will POST every action on the watched board, list, or card to it. One detail to know: at creation Trello sends an HTTP HEAD request to the callback and requires a 200 response, or the webhook is not created.
How is the credential handled? Trello puts it in the query string.
Trello's API authenticates with the key and token as query parameters on every request, which is a leakier shape than a header, so the connector wraps it in four layers of protection: the values are never concatenated into a URL string, error messages and logged lines are scrubbed of both values before anything is stored, both halves are registered with the execution's redaction layer so persisted outputs and logs are scrubbed again, and node configuration cannot override or expose the stored credential. The credential itself is stored encrypted, with the API key as the username and the token as the password.
Can I attach files to cards?
By URL only. Trello: Attach URL to Card stores a link on the card; Trello's multipart file upload is deliberately not exposed, because workflows pass data by value and by URL, not as file bytes. The flip side shows up on deletion: Trello: Delete Attachment is flagged destructive because a link attachment can be re-added but a file that was uploaded to Trello is permanently gone, and the node cannot know which kind it is deleting.
Why did updating a card wipe its labels or members?
Because the idLabels and idMembers fields on Trello: Update Card replace the entire set, which is how Trello's API defines them. When the intent is to change one thing, use Trello: Add Label to Card, Trello: Remove Label from Card, Trello: Add Member to Card, or Trello: Remove Member from Card: each changes exactly one thing and running the counterpart restores the previous state exactly.
Put Trello to work inside your workspace
Connect once, then use every node in visual automations and AI agent workflows across the Mattering platform.
All product names, logos, and brands are property of their respective owners and are used for identification purposes only. Use of these names, logos, and brands does not imply endorsement or affiliation. Trello is a product of its respective owner; Mattering is an independent platform.