Trello MCP server

A minimal remote MCP server that lets Claude manage your Trello boards, lists, and cards. Built with the MCP TypeScript SDK (Streamable HTTP transport, stateless mode).

Tools

• list_boards — list your open boards
• list_lists — lists (columns) on a board
• list_cards — cards in a list
• get_card — full card details
• create_card — create a card in a list
• update_card — edit / move / archive a card
• comment_card — add a comment
• search_cards — search cards across boards

1. Get Trello credentials

1. API key: go to https://trello.com/power-ups/admin, create a Power-Up, open its API key tab, and copy the key. (The older https://trello.com/app-key may still work.)

2. Token: visit this URL in your browser, replacing YOUR_KEY, then click Allow:

   https://trello.com/1/authorize?expiration=never&scope=read,write&response_type=token&name=Claude%20MCP&key=YOUR_KEY
   

   Copy the token it shows you.

scope=read,write grants Claude the ability to create/move/archive cards. Use scope=read if you want read-only.

2. Run locally (test)

cp .env.example .env      # fill in TRELLO_API_KEY, TRELLO_TOKEN, MCP_SECRET
npm install
npm run dev

Server prints the path it's serving (/mcp/<secret>).

3. Deploy

The server must be reachable over the public internet from Anthropic's cloud — it cannot be behind a VPN/firewall. Any Node host works (Railway, Render, Fly.io, a VPS).

Railway / Render (quick):

1. Push this folder to a GitHub repo.
2. Create a new service from the repo. Build: npm install && npm run build. Start: npm start. (Or use the included Dockerfile.)
3. Set env vars: TRELLO_API_KEY, TRELLO_TOKEN, MCP_SECRET. The host sets PORT automatically.
4. Note your public URL, e.g. https://trello-mcp.up.railway.app.

Your connector URL is then:

https://<your-host>/mcp/<MCP_SECRET>

4. Add to Claude (Team plan — Owner)

1. Organization settings → Connectors → + Add → Custom.
2. Name it (e.g. "Trello"), paste the connector URL from step 3.
3. Save. Members can then enable it per chat via the + / Connectors button.

Security notes

• The connector URL is the credential. On Team plans every member can see the connector URL, and Claude's MCP client doesn't send custom auth headers — that's why the secret lives in the URL path. Treat the URL like a password.
• There is no per-user scoping: anyone with the URL acts as the single Trello account whose token you configured.
• Use scope=read if you don't want Claude making changes.
• Rotate by changing MCP_SECRET (and revoking the Trello token at https://trello.com/your/account) if the URL leaks.