Connect your AI Agents to Trello in minutes
Available tools
list_boards
List all boards accessible to the authenticated member. Returns boards with their names, descriptions, membership status, and configuration. Use filter parameter to show only open, closed, starred, or all boards. This is the primary way to discover what boards exist and get their IDs for subsequent operations.
get_board
Get detailed information about a specific board by its ID. Returns comprehensive board data including name, description, preferences, labels, memberships, and optional nested resources like lists, cards, and members. Use this to inspect board configuration or retrieve board details before performing operations.
create_board
Create a new Trello board with the specified name and optional configuration. You can set the board's description, organization, privacy level, default labels and lists, background color, and various preferences. Returns the created board with its new ID.
update_board
Update an existing board's properties such as name, description, closed status (archive/unarchive), organization, and various preferences including permission level, background, voting, and comments settings. Also allows updating label names directly on the board.
delete_board
Permanently delete a board and all of its contents including lists, cards, checklists, labels, and all associated data. This action cannot be undone. Consider archiving (closing) the board instead if you may need to recover it later.
get_board_lists
Get all lists on a specific board. Lists represent workflow columns like 'To Do', 'In Progress', 'Done'. Returns lists with their names, positions, and optional card data. Use filter to show only open, closed, or all lists.
get_board_cards
Get all cards on a specific board across all lists. Returns cards with their names, descriptions, due dates, labels, members, and positions. Use filter to show only open, closed, or all cards. Supports pagination with before/since parameters.
get_board_members
Get all members of a specific board. Returns member information including usernames, full names, avatars, and membership types. Members are users who have access to view and/or edit the board based on their permissions.
add_board_member
Add a member to a board with a specified membership type (admin, normal, or observer). The member must already exist in Trello. Use the member's Trello ID, username, or email address to identify them.
remove_board_member
Remove a member from a board, revoking their access to view or edit the board and its contents. The member will no longer see this board in their boards list and cannot access any cards or lists on it.
get_board_labels
Get all labels defined on a specific board. Labels are colored tags used to categorize cards. Returns label names, colors, and IDs. Boards start with default color labels that can be renamed or have additional labels added.
get_card
Get detailed information about a specific card by its ID. Returns comprehensive card data including name, description, due date, labels, assigned members, checklists, attachments, position, and more. Use optional parameters to include related resources like actions, board, or list details.
create_card
Create a new card on a list. Cards are the primary units of work in Trello. Specify the list, name, and optional properties like description, due date, start date, labels, assigned members, position, and location. You can also create a card by copying from another card or attaching a URL.
update_card
Update an existing card's properties including name, description, due date, start date, position, labels, assigned members, cover image, and more. Can also move a card to a different list or board by updating idList or idBoard. Set due to null to remove a due date.
delete_card
Permanently delete a card and all of its contents including comments, checklists, attachments, and activity history. This action cannot be undone. Consider archiving the card instead if you may need to recover it later.
archive_card
Archive or unarchive a card. Archived cards are hidden from the board and list views but can be restored later. All card data including comments, checklists, and attachments are preserved. Use value=True to archive or value=False to restore.
move_card
Move a card to a different list, optionally specifying a position (top, bottom, or numeric) within the target list. This changes the card's workflow stage while keeping all other card properties intact.
add_card_member
Add a member to a card, assigning them to the task. The member must already be a member of the board containing the card. Multiple members can be assigned to a single card.
remove_card_member
Remove a member from a card, unassigning them from the task. The member will no longer receive notifications for this card and will not appear in the card's member list.
add_card_label
Add a label to a card for categorization. The label must already exist on the board. Labels help visually categorize cards and can be used for filtering. Multiple labels can be added to a single card.
remove_card_label
Remove a label from a card. The label itself is not deleted from the board, only removed from this specific card. Other cards with the same label are not affected.
get_card_comments
Get all comments (actions of type commentCard) on a specific card. Returns comment text, author information, and timestamps. Supports pagination with limit, before, and since parameters for cards with many comments.
add_card_comment
Add a comment to a card. Comments provide a way to discuss the card with team members, leave notes, or document decisions. The comment will include the author and timestamp automatically.
update_card_comment
Update an existing comment on a card. Only the comment author can edit their comments. The comment will show an 'edited' indicator after modification.
delete_card_comment
Delete a comment from a card. Only the comment author or board admins can delete comments. Deleted comments cannot be recovered.
get_card_attachments
Get all attachments on a specific card. Returns attachment information including file names, URLs, types, sizes, and preview images. Attachments can be files uploaded to Trello or links to external resources.
add_card_attachment
Add an attachment to a card via URL. You can attach links to external resources like documents, images, or websites. Optionally set the attachment as the card's cover image. For file uploads, the URL should point to an accessible file.
delete_card_attachment
Delete an attachment from a card. The attached file or link will be removed and cannot be recovered. If the attachment was the card's cover, the cover will be removed as well.
get_card_checklists
Get all checklists on a specific card. Returns checklist names, items, completion status, and positions. Checklists help break down cards into smaller, trackable tasks.
create_checklist
Create a new checklist on a card. Checklists help break down cards into smaller, trackable tasks. Specify the card ID, checklist name, and optional position. You can also copy items from another checklist using idChecklistSource.
update_checklist
Update an existing checklist's name or position on the card. Changes to the checklist name are reflected immediately. Position determines the order of checklists on the card.
delete_checklist
Delete a checklist from a card. All check items within the checklist will also be deleted. This action cannot be undone.
add_checklist_item
Add a new item to a checklist. Check items represent individual tasks or steps within a checklist. You can set the initial state (checked/unchecked), due date, and assign a member to the item.
update_checklist_item
Update a checklist item's name, state (complete/incomplete), position, due date, or assigned member. Use this to mark items complete, rename them, or change their assignment. Items are updated on the card they belong to.
delete_checklist_item
Delete an item from a checklist. The item will be permanently removed from the checklist. This action cannot be undone.
create_label
Create a new label on a board. Labels are colored tags used to categorize cards. Specify the board, optional name, and color. Available colors: green, yellow, orange, red, purple, blue, sky, lime, pink, black. Use null color for a colorless label.
update_label
Update an existing label's name or color. You can change the label text, change its color, or set color to null to remove the color. Changes affect the label everywhere it is used on cards.
delete_label
Delete a label from a board. The label will be removed from all cards that have it applied. This action cannot be undone.
get_list
Get detailed information about a specific list by its ID. Returns the list's name, position, closed status, parent board ID, and subscription status. Use this to inspect list properties before making changes.
create_list
Create a new list on a board. Lists are the vertical columns that contain cards, typically representing workflow stages. Specify the list name, parent board, and optional position (top, bottom, or numeric position value).
update_list
Update an existing list's properties including name, position, closed status (archive/unarchive), and subscription status. Can also move a list to a different board by specifying a new board ID.
archive_list
Archive or unarchive a list. Archived lists are hidden from the board view but can be restored later. All cards within an archived list remain intact but are also hidden. Use value=True to archive or value=False to restore.
move_list
Move a list to a different board. All cards within the list will also be moved to the target board. The list will appear at the end of the target board's lists by default.
get_list_cards
Get all cards in a specific list. Returns cards with their names, descriptions, due dates, labels, members, and positions within the list. Use filter to show only open, closed, or all cards in the list.
get_member
Get detailed information about a specific Trello member by their ID or username. Returns profile information including full name, username, avatar, bio, and optionally their boards and organizations. Use 'me' as the ID to get the current authenticated user.
get_current_member
Get information about the currently authenticated Trello member (the user whose API token is being used). This is equivalent to calling get_member with ID 'me'. Returns the user's profile, boards, and organizations.
search_members
Search for Trello members by name or username. Returns matching members with their basic profile information. Can optionally limit search to members of a specific board or organization.
search
Search across Trello for boards, cards, members, and organizations. Supports powerful search operators like @username, #label, board:id, list:name, is:open, is:archived, has:attachments, due:day, due:week, and more. Results can be filtered by specific boards or organizations.
validate_credential
Validate Trello credentials. Verifies credentials during setup.
How to set up Merge Agent Handler
In an mcp.json file, add the configuration below, and restart Cursor.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}
11Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.
Make sure Claude is using the Node v20+.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "yMt*****"
14 }
15 }
16 }
17}Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "<ah-production-access-key>"
14 }
15 }
16 }
17 }In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".
You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.
Learn more in the official documentation ↗
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "agent-handler-auth",
6 "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7 "password": true
8 }
9 ],
10 "servers": {
11 "agent-handler": {
12 "type": "stdio",
13 "command": "npx",
14 "args": [
15 "-y",
16 "mcp-remote@latest",
17 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18 "--header",
19 "Authorization: Bearer ${input:agent-handler-auth}"
20 ]
21 }
22 }
23}FAQs on using Merge's Trello MCP server
FAQs on using Merge's Trello MCP server
What is a Trello MCP?
It's an MCP server that connects your agents to Trello via tools. Your agents can invoke these tools to create and update cards, move cards across lists, manage board members, add comments, and track checklist progress, and more.
Atlassian doesn't offer an MCP server purpose built for Trello, but you can use one from a third-party platform, like Merge Agent Handler.
How can I use the Trello MCP server?
The use cases naturally depend on the agent you've built, but here are a few common ones:
- Automated card creation from support tickets: When a new bug is filed in Zendesk, an agent calls <code class="blog_inline-code">
create_card</code>to open a corresponding card in the engineering team's Trello board, pre-populated with the ticket title, description, and priority label
- Sprint progress digest: Each Friday, an agent calls <code class="blog_inline-code">
get_board_cards</code>to pull all cards across lists, tallies completion by status, and posts a structured summary to Slack so the team has a weekly snapshot without a manual standup
- Cross-tool status sync: When a deal closes in Salesforce, an agent calls <code class="blog_inline-code">
create_card</code>to add an onboarding card to the customer success board, assigns the relevant team member via <code class="blog_inline-code">add_card_member</code>, and attaches the contract link using <code class="blog_inline-code">add_card_attachment</code>
- Checklist-driven workflow tracking: An agent monitors <code class="blog_inline-code">
get_card_checklists</code>for a set of cards, detects when all checklist items are complete, and automatically calls <code class="blog_inline-code">move_card</code>to advance the card to the next list without manual intervention
What are popular tools for Trello's MCP server?
Here are some of the most commonly used tools:
<code class="blog_inline-code">create_card</code>adds a new card to a specified Trello list with a title, description, and optional labels or members. Use this when an agent needs to create a task in response to an event in another system
<code class="blog_inline-code">update_card</code>modifies an existing card's fields including title, description, due date, and position. Useful for agents that need to keep Trello cards in sync with data from an external source
<code class="blog_inline-code">move_card</code>transfers a card to a different list or board. Call this when an agent needs to advance a card through a workflow stage based on a condition met elsewhere
<code class="blog_inline-code">get_board_cards</code>retrieves all cards on a board, optionally filtered by list. Good for agents that need to generate a status report or check the current state of work before taking an action
<code class="blog_inline-code">add_card_comment</code>posts a comment to a specific card. Helpful when an agent needs to log an update, record a decision, or surface information from another tool directly on the relevant card
<code class="blog_inline-code">get_card_checklists</code>returns all checklists and their item completion status for a card. Use this when an agent needs to determine whether a card is ready to advance or requires follow-up before moving forward
What makes Merge Agent Handler's Trello MCP server better than alternative Trello MCP servers?
Here is what sets Merge Agent Handler's Trello MCP server apart from building your own or using a standalone alternative:
- Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Trello, this means you can prevent card descriptions, attachments, and member data from being exposed even when the agent has broad read access
- Managed authentication and credentials: Merge stores and refreshes Trello credentials on your behalf. You never expose API keys or OAuth tokens to an agent or handle re-authentication when credentials change
- Real-time observability and audit trail: Every tool call made against Trello is logged with timestamp, tool name, input parameters, and response metadata. You can see exactly what cards an agent created, moved, or commented on without adding any custom logging
- Tool Packs and controlled access: Tool Packs let you bundle specific Trello tools with tools from other connectors into a single MCP endpoint, scoped to a specific use case. An agent gets exactly the tools it needs, nothing more
How can I start using Merge Agent Handler's Trello MCP server?
You can take the following steps:
1. Create or log into your Merge Agent Handler account and navigate to Tool Packs (collections of connector tools scoped to a specific use case).
2. Create a new Tool Pack, then find and enable the Trello connector. Choose which tools to include; enable read tools like <code class="blog_inline-code">get_board_cards</code> for reporting use cases, or add write tools like <code class="blog_inline-code">create_card</code> and <code class="blog_inline-code">move_card</code> if your agent needs to create or advance cards.
3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.
4. From the Registered User detail page, authenticate Trello by completing the OAuth flow. Merge stores and manages the credentials going forward.
5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.
6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Trello tools are now accessible through that endpoint.
Ready to try it out?
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now
