Trello MCP Server — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Dated implementation activity and relevant MCP role justify continued Radar monitoring.

Reviewed Oct 9, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Create and manage Trello cards, lists, workspaces and comments

What we know

Community Trello MCP exposing board/card CRUD, acceptance criteria, comments, checklists and advanced workflow tools.

Maintenance / activity evidence

GitHub REST repository pushed_at 2026-09-23T19:51:44Z for delorenj/mcp-server-trello

Tracking evidence observed Oct 9, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Create/update/archive boards/cards/lists; manage comments Reported action classes: Create/update/archive boards/cards/lists; manage comments. Complete write authority is not verified.
Trello API key and user token
Sensitive access: Workspace/card data, User token, Attachments

Avoid granting broader Trello scopes than necessary
Trello boards and cards may be created, modified, archived or deleted where token permits; use limited workspace scopes.
Trello API key and token permit card/board mutations; workspace allowlist supported.
Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

445 repository stars · 12.6k package downloads / 30 days

Stars observed Oct 9, 2026. Downloads observed Oct 9, 2026.

Repository total for delorenj/mcp-server-trello.

Exact npm package @delorenj/mcp-server-trello; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

At the next review, has this exact implementation gained new releases, changed setup/security scope, or become suitable for Shortlist?

No verified blocker to PUBLIC RADAR TRACKING within the bounded first-party evidence reviewed; material permissions and mitigations are explicitly disclosed.

Avoid granting broader Trello scopes than necessary
Trello boards and cards may be created, modified, archived or deleted where token permits; use limited workspace scopes.
Trello API key and token permit card/board mutations; workspace allowlist supported.
Create/update/archive boards/cards/lists; manage comments
Trello API key and user token
Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Reviewed write actions: Create/update/archive boards/cards/lists; manage comments
Sensitive access: Workspace/card data, User token, Attachments
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Needs Trello API key and token
Writes can move/archive work records
Respect scoped token and workspace access
No independent release lifecycle audit; do not claim precise activity date.

Original activity observations

GitHub REST repository pushed_at 2026-09-23T19:51:44Z for delorenj/mcp-server-trello

Technical identity

github.com/delorenj/mcp-server-trello

Exact implementation source: https://www.npmjs.com/package/@delorenj%2Fmcp-server-trello ↗
Reviewed resource type: MCP Server
Repository identity: delorenj/mcp-server-trello
Package identity: npm:@delorenj/mcp-server-trello

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 9, 2026 · Latest source observation Oct 9, 2026

GitHub repository ↗
delorenj/mcp-server-trello
Recorded repository material and project history.
Package registry ↗
@delorenj/mcp-server-trello
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Claude Code

Publisher instructions with a documented client setup path.

Source evidence observed Oct 12, 2026.

Additional setup details required — see the specific gaps below.

Warning

Trello token may grant write capabilities; revoke separately in Trello account.
Exact vendor-specific credential revoke procedure not established from checked official Setup documentation; may be external or not applicable. Do not invent.
publisher README config shape Replace the supplied credential/path placeholders privately; use only the named configuration schema.
Run the removal command in the same client and configuration scope used for registration; this does not uninstall an application, revoke third-party authorization, or delete data.
Avoid exposing tokens in shell history or checked-in JSON.
MCP100 client-scope note: this Claude Code CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry. Replace the supplied angle-bracket placeholders privately before using this template; keep credentials out of shell history and shared configuration.
MCP100 client-scope note: this Claude Code CLI example applies only to that client and the exact registered name in the command. Desktop, Cursor and other clients use their own configuration; do not run it for a differently named entry. Run the removal command in the same client and configuration scope used for registration; this does not uninstall an application, revoke third-party authorization, or delete data.

Install / connect
Publisher instructions
Publisher-specific setup path. Follow prerequisites, then register or connect to your MCP host.
claude mcp add trello --env TRELLO_API_KEY=<KEY> --env TRELLO_TOKEN=<TOKEN> -- bunx @delorenj/mcp-server-trello
Configure / authenticate
Publisher instructions
Obtain Trello key and token via trello.com/app-key; use Bun (`bunx`) or equivalent npx MCP configuration.
Advanced configuration · claude desktop json · Publisher instructions
claude desktop json · Publisher instructions
{ "mcpServers": { "trello": { "args": [ "@delorenj/mcp-server-trello" ], "command": "bunx", "env": { "TRELLO_API_KEY": "your-trello-api-key", "TRELLO_TOKEN": "your-trello-token" } } } }
Check connection
Suggested check
Discover Trello tools and list available boards (read-only).
Remove / uninstall / revoke
MCP100 setup guide
`claude mcp remove trello` unregisters the Claude Code MCP entry; does not delete Trello boards.
MCP100 client-scope guidance: each CLI removal example targets only its named client and exact registered entry. Package names, Desktop/Cursor configuration keys and Codex/Claude registration names may differ; use the entry you actually registered. Client removal does not revoke provider credentials.
claude mcp remove trello

Official Documentation & Sources

What it does

Community Trello MCP exposing board/card CRUD, acceptance criteria, comments, checklists and advanced workflow tools.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Create and manage Trello cards, lists, workspaces and comments

Representative uses

List boards and cards
Update checklists
Write comments
Archive cards/lists
Manage custom fields

Limitations

Needs Trello API key and token
Writes can move/archive work records
Respect scoped token and workspace access
Avoid granting broader Trello scopes than necessary
No independent release lifecycle audit; do not claim precise activity date.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Trello API key and user token
Permissions: Create/update/archive boards/cards/lists; manage comments
Data handling: Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component.
Cost: unknown
Risk and cautions: Avoid granting broader Trello scopes than necessary

Access scope and cautions

Write actions: Not verified Create/update/archive boards/cards/lists; manage comments
Sensitive access: Workspace/card data User token Attachments
Risk level: high
Security notes: Trello boards and cards may be created, modified, archived or deleted where token permits; use limited workspace scopes. Trello API key and token permit card/board mutations; workspace allowlist supported.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-09. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: List boards and cards; Update checklists; Write comments; Archive cards/lists; Manage custom fields.

What setup and authentication are documented?

Recorded installation/entrypoint step: bunx @delorenj/mcp-server-trello. Recorded transport: stdio. Recorded environment-variable notes: TRELLO_API_KEY; TRELLO_TOKEN. No configuration values are supplied here. Prerequisites: Compatible MCP client. Client notes: Source docs and package may evolve; install according to confirmed release. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: Trello API key and user token

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Create/update/archive boards/cards/lists; manage comments. Recorded permission context: Create/update/archive boards/cards/lists; manage comments

What data-handling boundary should I consider?

Depends on configured local process, connected account and remote APIs; review first-party privacy terms for any hosted component. Recorded sensitive-access context: Workspace/card data; User token; Attachments.

What limitations and risks should I check before use?

Avoid granting broader Trello scopes than necessary. Needs Trello API key and token. Writes can move/archive work records. Respect scoped token and workspace access. No independent release lifecycle audit; do not claim precise activity date. Trello boards and cards may be created, modified, archived or deleted where token permits; use limited workspace scopes. Trello API key and token permit card/board mutations; workspace allowlist supported. Unknown vulnerabilities and client-side tool approvals were not exhaustively evaluated.