Home / MCP / Trelo MCP Server

Trelo MCP Server

Provides Trello board/card operations, comments, attachments, and activity with rate limiting and type safety.

typescript

178stars

View on GitHub

Installation

Add the following to your MCP client configuration file.

Configuration

View docs

{
    "mcpServers": {
        "trello": {
            "command": "bunx",
            "args": [
                "@delorenj/mcp-server-trello"
            ],
            "env": {
                "TRELLO_API_KEY": "your-api-key",
                "TRELLO_TOKEN": "your-token"
            }
        }
    }
}

You can connect your Trello workspace to an MCP client via a Trello MCP Server. It exposes a rich set of Trello actions, including board/list/card operations, attachments, comments, and activity retrieval, all with built‑in validation and rate‑limit handling so you can automate Trello workﬂows safely.

How to use

Use an MCP client to discover and start the Trello MCP Server, then invoke endpoints as needed. You typically run a local or remote stdio server process and reference its endpoints by name in your MCP configuration. When you start the server, you provide your Trello API credentials and the server will handle Trello API interactions, rate limiting, and error reporting. You can switch active boards and workspaces at runtime without restarting the server.

Key usage patterns include: selecting an active board, listing boards and workspaces, fetching detailed card data, updating cards, attaching files, and managing comments. Operations are exposed as distinct tools/endpoints that you call via your MCP client, with input validation and helpful error messages when something goes wrong.

How to install

Prerequisites you need before starting: Bun runtime (v1.0.0 or higher) or Node.js for alternative npm/npx workflows. A working Trello API key and Trello token for authentication.

Choose an installation method and follow the steps exactly as shown.

Configuration and runtime notes

Environment values you must provide to connect to Trello fall under two required keys: TRELLO_API_KEY and TRELLO_TOKEN. These must be supplied to the server so Trello requests can be authenticated.

Security and workflows

Token management is important. If you generate a never-expiring token, consider renewing it periodically for security reasons and ensure your deployment environment remains secure.

Examples and workflows

You can pair this Trello MCP Server with other MCP servers to enrich automation, such as generating images or content and attaching them to Trello cards. The examples illustrate multi-server configurations and how to coordinate actions across servers.

Available tools

list_boards

List all boards the user has access to.

set_active_board

Set the active board for future operations by providing a boardId.

list_workspaces

List all workspaces the user has access to.

set_active_workspace

Set the active workspace for future operations by providing a workspaceId.

get_active_board_info

Get information about the currently active board.

list_boards_in_workspace

List all boards within a specific workspace by workspaceId.

get_lists

Retrieve all lists from a board.

get_card

Get comprehensive details of a Trello card, including checklists, attachments, labels, members, comments, and more. Can return formatted Markdown if requested.

get_cards_by_list_id

Fetch all cards from a specific Trello list.

get_my_cards

Fetch all cards assigned to the current user.

add_card_to_list

Add a new card to a specified list with optional description, due date, start date, and labels.

update_card_details

Update an existing card's details, including name, description, due date, start date, completion status, and labels.

archive_card

Archive a card by moving it out of the active lists.

move_card

Move a card to a different list.

attach_image_to_card

Attach an image to a card from a URL with an optional attachment name.

attach_file_to_card

Attach any file to a card from a URL or local file path with optional name and mime type.