Trello MCP: community servers, setup, and what breaks

    No first-party server. Which community option to pick, and the board-permission traps.

    Community serversLast checked: September 2026

    We found no first-party Trello MCP server when we last checked. Several community servers exist on GitHub and are listed in the MCP directories; quality varies a lot between them.

    What it can do

    • List boards, lists and cards
    • Create cards and move them between lists
    • Add comments, labels and due dates
    • Read checklists on a card

    What it can't do

    • Community maintenance means a Trello API change can break the server with no warning
    • Most servers need both an API key and a token, and the token is easy to scope too narrowly
    • Power-Up data is usually invisible to the server, so automations built on Power-Ups will not see it

    Trello's MCP situation is the common one across this whole category: no first-party server, several community servers of uneven quality, and directory listings that do not tell you which is maintained. If you pick from a search result without checking, you will likely land on a repository whose last commit predates the current Trello API surface.

    How to choose between the community servers

    Three signals, in order. Recent commits inside the last couple of months, because the Trello API moves and dead servers fail silently. An explicit list of the tools the server exposes in the README, because a server that documents four tools and implements eleven is a server nobody has read recently. And a stated auth model — key plus token, with the scopes named. Anything asking for credentials without saying what it does with them is not worth the install.

    The permission trap

    Trello's token scopes are the single biggest source of "it connected but nothing works". A read-only token produces a server that lists boards perfectly and fails every write with an unhelpful error. If reads succeed and writes fail, regenerate the token with write scope before touching the config again.

    What it is genuinely good for

    Trello's structure — board, list, card — maps unusually well onto conversation. "Move everything in Review that has been there more than a week back to In Progress and comment why" is a sentence, and through MCP it is also an action. Reporting is the other strong case: asking for a summary of what moved this week is faster than reading the board.

    Where LemTask stands today

    LemTask does not ship an MCP server yet, and we are not going to pretend otherwise on a page developers will read. What LemTask has working right now is outbound and inbound webhooks, Zapier, Make and Apple Shortcuts, which covers "when a task is created, do X" and "create a task from anything that can send an HTTP request". An MCP connection is on the roadmap; when it ships and we have tested it end to end with Claude, this page will say so with the config block, and not a day earlier.

    Setup, step by step

    1. 1

      Pick a maintained server

      Compare the community servers on recent commit activity and on whether the README lists the tools it exposes. Avoid anything with no commits in the last few months.

    2. 2

      Generate a key and token with write scope

      Trello needs both. Create them from your Trello developer settings and make sure the token includes write access, not just read.

    3. 3

      Add the entry to your MCP client config

      Add the server with your key and token as environment variables, keeping the file valid JSON, then quit and reopen the client.

    4. 4

      Verify with one read and one write

      Ask it to list a board, then to add a test card. If only the read works, fix the token scope rather than the config.

    Questions

    Related pages

    Want a task app that automates today?

    LemTask has no MCP server yet. It does have webhooks, Zapier, Make and Apple Shortcuts working now, plus tasks, habits, a focus timer and calendar sync. Free forever for individuals.