trello-mcp-server

Cloud-hosted MCP server that exposes Trello operations as tools for Claude. Replaces the manual snapshot → propose → apply workflow.

Architecture

Claude (Code/Cowork) → HTTPS → Fly.io MCP Server → Trello API

Related MCP server: Trello MCP server

Disclaimer

This software is provided as-is, without warranty of any kind. Use at your own risk.

• Your credentials, your responsibility — you supply your own Trello API key/token and bearer token. Keep them secret; rotate them if compromised.

• Destructive actions are possible — Claude can archive cards, create boards, and modify data. Review the tools you expose and restrict board access as appropriate before connecting an AI agent.

• No affiliation — this project is not affiliated with, endorsed by, or supported by Trello or Atlassian.

• Self-hosted — when you deploy to Fly.io you run your own instance. The author does not operate a shared instance and has no access to your data or credentials.

See LICENSE for the full MIT license terms.

Tools

Setup

1. Prerequisites

• Fly.io account + flyctl installed

• Trello API key + token from https://trello.com/power-ups/admin

2. Deploy

git clone https://github.com/sens8tion/trello-mcp-server
cd trello-mcp-server

# Create the Fly app (first time only)
flyctl launch --no-deploy

# Set secrets
flyctl secrets set \
  TRELLO_API_KEY=your_key \
  TRELLO_TOKEN=your_token \
  MCP_AUTH_TOKEN=your_secret_bearer_token

# Deploy
flyctl deploy

3. Register in Claude MCP config

Run the helper to auto-detect your Claude Desktop config path and write the entry:

python register-mcp.py
# then restart Claude Desktop

Or add manually to your Claude MCP settings (e.g. ~/.claude/mcp_servers.json):

{
  "mcpServers": {
    "trello": {
      "command": "mcp-remote",
      "args": [
        "https://trello-mcp-server.fly.dev/mcp",
        "--transport",
        "http-only",
        "--header",
        "Authorization:Bearer your_secret_bearer_token"
      ]
    }
  }
}

Local dev

pip install -r requirements-dev.txt
cp .env.example .env  # fill in your values
python server.py

# Lint + test
ruff check .
pytest

Logging

Each tool emits a human-readable log entry via ctx.info() MCP context notifications — visible in the Claude Desktop log pane and any MCP-aware client.

Log messages describe the action taken (fetch, create, move, update, archive, etc.), making it easy to trace agent behaviour during a session. No secrets are logged; API keys and tokens remain in environment variables.

Example log output:

[list_cards] Fetching cards for list 63a1b2c3d4e5f6a7b8c9d0e1
[move_card] Moving card abc123 → list 63a1b2c3d4e5f6a7b8c9d0e1
[archive_card] Archiving card abc123

CI/CD

• CI runs on every push/PR: lint (ruff) + tests (pytest)

• Deploy runs on merge to main (after CI passes): flyctl deploy --remote-only

• Required GitHub secret: FLY_API_TOKEN

Future

• Ephemeral agent — instead of a persistent VM, the server runs as an on-demand process (e.g. Fly.io Machine spun up per invocation and destroyed on completion). Accepts a natural-language task, runs a Claude agentic loop to orchestrate Trello operations, then exits. No idle cost, no persistent state.