Trello MCP integration for AI agents.
Connect AI agents to Trello through 28 structured actions, including create list, add card attachment url, and archive card. Review authentication, inputs, w…
- ACTION CONTRACTS
- 28
- AUTHENTICATION
- Custom credentials
- SOURCE STATUS
- Provider-backed
CATALOG SOURCE REVIEWED AUGUST 23, 2026 / ACTION NAMES AND SCHEMAS DERIVED FROM WORKING MACHINES PROVIDER SOURCE
CAPABILITY PROFILE
What the Trello integration exposes
The Trello Agent App exposes 28 provider-backed actions for productivity work. Its current contract lets an authorized agent create a trello list on a board, attach an external url to a trello card, and archive a trello card. These operations are called through Working Machines as typed capabilities rather than through browser navigation or copied UI steps.
A connection uses Custom credentials. Before execution, the agent can inspect the selected action, its required fields, declared scopes, and expected output contract. Provider credentials remain inside the Working Machines runtime; the calling agent receives the capability and its structured result, not the underlying secret.
For reliable operation, start with the narrowest action that satisfies the task, resolve stable provider identifiers before changing state, and validate the returned object or status after execution. Availability still depends on the connected Trello account, granted provider permissions, workspace policy, region, plan, and upstream API behavior.
VERIFIED ACTION SAMPLE
Real Trello capabilities.
Showing 12 of 28 actions. Risk labels are conservative signals based on operation names, not substitutes for provider documentation or runtime policy.
create_listREADCreate a Trello list on a board.
INPUTS: boardId / name / position
add_card_attachment_urlWRITEAttach an external URL to a Trello card.
INPUTS: cardId / url / name
archive_cardHIGH IMPACTArchive a Trello card.
INPUTS: cardId
add_card_commentWRITEAdd a comment action to a Trello card.
INPUTS: cardId / text
add_card_labelWRITEAdd a Trello label to a card.
INPUTS: cardId / labelId
add_card_memberWRITEAssign a Trello member to a card.
INPUTS: cardId / memberId
add_checkitemWRITEAdd a check item to a Trello checklist.
INPUTS: checklistId / name / position / checked
archive_listHIGH IMPACTArchive a Trello list.
INPUTS: listId
create_boardWRITECreate a Trello board.
INPUTS: name / description / defaultLists / permissionLevel
create_cardWRITECreate a Trello card in a list.
INPUTS: listId / name / description / due / position
create_checklistWRITECreate a Trello checklist on a card.
INPUTS: cardId / name
get_boardREADGet a Trello board by ID.
INPUTS: boardId / fields
INPUT CONTRACTS
Know what the action needs before it runs.
create_list
boardIdREQUIRED- Trello board ID that will own the list.
nameREQUIRED- List name.
positionOPTIONAL- List position. Use top, bottom, or a numeric position.
add_card_attachment_url
cardIdREQUIRED- Trello card ID or short link.
urlREQUIRED- URL to attach to the card.
nameOPTIONAL- Attachment display name.
archive_card
cardIdOPTIONAL- Trello card ID or short link.
add_card_comment
cardIdOPTIONAL- Trello card ID or short link.
textOPTIONAL- Comment text to add to the card.
PROVIDER-SPECIFIC WORKFLOWS
Jobs this Agent App can support
Inspect Create List
Create a Trello list on a board. Use this as a bounded discovery step, retain the returned identifier, and avoid expanding the read beyond the task's stated scope.
create_listControl Add Card Attachment Url
Attach an external URL to a Trello card. Resolve the target first, present material changes for confirmation, and make retries idempotent where the provider supports it.
add_card_attachment_urlVerify with Add Card Attachment Url
Attach an external URL to a Trello card. Compare the returned provider state with the intended outcome and preserve stable IDs or canonical links in the run record.
add_card_attachment_urlSAFETY BOUNDARY
Operate Trello with explicit limits
- Authorize Trello with Custom credentials and grant only the provider access required by the selected actions.
- 15 actions are change-capable by name. Confirm the target identity and material parameters before allowing a write.
- Treat `archive_card`, `archive_list`, and `remove_card_label` as high-impact operations and require an explicit approval boundary.
- No provider scope string is declared on the sampled actions. Verify the connected account's actual permissions in Trello rather than assuming unrestricted access.
- After a call, inspect the structured result and execution record before reporting that the Trello task completed successfully.
CONNECTION MODEL
Custom credentials
Trello uses Custom credentials. Connection requirements and availability are determined by the provider and the Working Machines deployment.
Working Machines stores provider credentials behind the execution boundary. An agent can use an authorized connection identity, but catalog discovery alone does not reveal OAuth tokens, API keys, or provider secrets.
- READ SIGNALS
- 13
- WRITE SIGNALS
- 11
- HIGH IMPACT
- 4
- REVIEW SIGNALS
- 0
EVIDENCE AND AVAILABILITY
Provider reference
Action names, input fields, authentication types, and counts on this page are generated from the Working Machines provider catalog. Provider behavior, quotas, object semantics, account eligibility, and regional availability remain governed by Trello.