Skip to main content
Glama

trello-mcp

A Codex-first Trello MCP server for AI agents

Codex ready MCP server Trello Node.js License: MIT

trello-mcp gives Codex and other MCP-compatible AI agents a clean, practical way to inspect and update Trello boards through Trello's official REST API.

Why This Exists

AI agents are useful when they can see the real workflow, not just the codebase. This server lets Codex connect to Trello so it can understand tasks, keep cards updated, add evidence comments, and help maintain project boards without scraping or browser automation.

It is designed for Codex first, but it works as a normal stdio MCP server in any client that supports the Model Context Protocol.

Related MCP server: Trello MCP Server

Features

Area

Supported actions

Account

Identify the authenticated Trello member

Workspaces

List visible Trello workspaces

Boards

List open boards and inspect board metadata

Lists

List board columns/lists

Cards

List, read, search, create, update, move, comment on, and archive cards

Checklists

Create checklists and checklist items

Agent safety

Redacted errors, no committed credentials, archive-first workflow guidance

Tool List

Tool

Purpose

trello_whoami

Show the authenticated Trello member

trello_list_workspaces

List visible Trello workspaces

trello_list_boards

List open Trello boards

trello_get_board

Read board metadata

trello_list_lists

List board lists

trello_list_cards

List cards, optionally by list

trello_get_card

Read a card

trello_search_cards

Search cards by text

trello_create_card

Create a card

trello_update_card

Update card title, description, due date, or archive state

trello_move_card

Move a card to another list

trello_add_comment

Add a card comment

trello_archive_card

Archive a card

trello_add_checklist

Add a checklist to a card

trello_add_check_item

Add an item to a checklist

Quick Start

git clone https://github.com/KharalDipendra/trello-mcp.git
cd trello-mcp
npm install
npm run build

Run the local verification suite:

npm run check

Trello Credentials

You need a Trello API key and token.

  1. Open Trello's API key page: trello.com/app-key

  2. Copy your API key.

  3. Generate a token using this URL after replacing YOUR_API_KEY:

https://trello.com/1/authorize?expiration=never&name=trello-mcp&scope=read,write&response_type=token&key=YOUR_API_KEY

Required environment variables:

TRELLO_API_KEY=your_trello_api_key
TRELLO_TOKEN=your_trello_token

Optional environment variables:

TRELLO_BOARD_ID=default_board_id
TRELLO_IDENTITY=default
TRELLO_BASE_URL=https://api.trello.com/1

Never commit a real .env file. Keep Trello credentials in your MCP client config, shell environment, or secret manager.

Codex Setup

Build the project first:

npm install
npm run build

Then add an MCP server entry to your Codex config:

{
  "mcpServers": {
    "trello": {
      "command": "node",
      "args": ["/absolute/path/to/trello-mcp/dist/index.js"],
      "env": {
        "TRELLO_API_KEY": "your_trello_api_key",
        "TRELLO_TOKEN": "your_trello_token",
        "TRELLO_BOARD_ID": "optional_default_board_id",
        "TRELLO_IDENTITY": "default"
      }
    }
  }
}

For Windows paths, use escaped backslashes or forward slashes:

"args": ["C:/Users/you/Desktop/trello-mcp/dist/index.js"]

Multiple Trello Accounts

Run one MCP entry per Trello identity:

{
  "mcpServers": {
    "trello-personal": {
      "command": "node",
      "args": ["/absolute/path/to/trello-mcp/dist/index.js"],
      "env": {
        "TRELLO_API_KEY": "key_for_account_one",
        "TRELLO_TOKEN": "token_for_account_one",
        "TRELLO_IDENTITY": "account-one"
      }
    },
    "trello-work": {
      "command": "node",
      "args": ["/absolute/path/to/trello-mcp/dist/index.js"],
      "env": {
        "TRELLO_API_KEY": "key_for_account_two",
        "TRELLO_TOKEN": "token_for_account_two",
        "TRELLO_IDENTITY": "account-two"
      }
    }
  }
}

Standalone MCP Usage

The server communicates over stdio, so it is normally launched by an MCP client.

TRELLO_API_KEY=... TRELLO_TOKEN=... node dist/index.js

You can also run the TypeScript source during development:

TRELLO_API_KEY=... TRELLO_TOKEN=... npm run dev

Agent Safety Model

trello-mcp is intentionally simple and explicit:

  • It uses Trello's REST API directly.

  • It does not scrape Trello pages.

  • It does not store credentials.

  • It redacts credentials from Trello API error messages.

  • It exposes archive tools, not permanent delete tools.

  • It encourages agents to inspect board state before changing cards.

Recommended agent behaviour:

  1. Read the board, lists, and relevant cards first.

  2. Explain planned changes before writing when the workflow is sensitive.

  3. Add short evidence comments for meaningful card updates.

  4. Move cards to done only when the underlying work is actually complete.

  5. Prefer archiving stale cards over deleting them.

Development

npm install
npm run check

Available scripts:

Script

Description

npm run build

Compile TypeScript into dist/

npm test

Run mocked client tests

npm run check

Build and test

npm run dev

Run the MCP server from TypeScript

npm start

Run the compiled MCP server

The test suite uses mocked Trello responses and does not call the live Trello API.

Project Structure

trello-mcp/
  examples/
    codex-mcp.json
  src/
    index.ts
    trelloClient.ts
  test/
    trelloClient.test.ts

Contributing

Issues and pull requests are welcome. Keep changes generic and avoid committing board data, workspace names, real card content, tokens, or account-specific config.

License

MIT. See LICENSE.

Available Tools

15 tools
trello_add_check_itemAdd Checklist ItemB

Add an item to an existing Trello checklist.

Inputs: name (required), checklistId (required), checked.

trello_add_checklistAdd Card ChecklistB

Add a checklist to a Trello card.

Inputs: name (required), cardId (required).

trello_add_commentAdd Card CommentB

Add a comment to a Trello card.

Inputs: text (required), cardId (required).

trello_archive_cardArchive Trello CardA

Archive a Trello card. Prefer this over permanent deletion.

Inputs: cardId (required).

trello_create_cardCreate Trello CardB

Create a card by list id or by exact list name.

Inputs: name (required), due, listId, boardId, +2 more.

trello_get_boardGet Trello BoardB

Return metadata for a Trello board.

Inputs: boardId.

trello_get_cardGet Trello CardC

Return key details for a Trello card.

Inputs: cardId (required).

trello_list_boardsList Trello BoardsA

List open Trello boards visible to the authenticated member.

Inputs: no named parameters.

trello_list_cardsList Board CardsB

List cards on a board, optionally filtered by exact list name.

Inputs: boardId, listName, includeClosed.

trello_list_listsList Board ListsC

List lists on a Trello board.

Inputs: boardId.

trello_list_workspacesList Trello WorkspacesA

List Trello workspaces visible to the authenticated member.

Inputs: no named parameters.

trello_move_cardMove Trello CardB

Move a card to a destination list id or exact list name.

Inputs: cardId (required), listId, boardId, listName.

trello_search_cardsSearch Trello CardsA

Search cards by text. Uses TRELLO_BOARD_ID when boardId is omitted.

Inputs: query (required), limit, boardId.

trello_update_cardUpdate Trello CardB

Update a Trello card title, description, due date, or archive state.

Inputs: cardId (required), due, name, closed, +1 more.

trello_whoamiCurrent Trello MemberA

Return the Trello member authenticated for this MCP server.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool targets a distinct action on a specific Trello resource (board, list, card, checklist, comment, user). No two tools have overlapping purposes; even closely related tools like 'get_card' and 'list_cards' are clearly differentiated by scope.

    Naming Consistency5/5

    All tools follow a consistent 'trello_verb_noun' pattern using lowercase with underscores. Verbs are imperative and descriptive (add, archive, create, get, list, move, search, update, whoami), with no mixing of conventions.

    Tool Count5/5

    With 15 tools, the set covers the primary Trello workflows (boards, lists, cards, checklists, comments, search, user info) without being bloated. Each tool serves a clear purpose within the domain.

    Completeness4/5

    The tool set covers core operations for cards (CRUD + move/archive/search), checklists, comments, and boards (list/get). Missing board/list creation and deletion, but these are less common for typical agent tasks. Archiving is preferred over deletion, which is reasonable.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Trello boards, lists, and cards through the Trello REST API. Supports board management, card operations, member management, labels, and checklists through natural language.
      96 npm
      1
      ISC
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides seamless integration with Trello's API to manage boards, lists, and cards through natural language. It supports full CRUD operations, card movement, and the ability to load Trello resources directly into an LLM's context for analysis.
      MIT