MCP server for Trello boards, cards, lists, comments, checklists, attachments, labels, board activity, workspace selection, and rate-limited Trello API automation from Claude.
Trello MCP Server can create, read, update, move, archive, and delete board data depending on token permissions and requested tools., Card, checklist, label, due-date, start-date, comment, attachment, board, list, workspace, and active-board changes can affect real team workflows., File attachments are added from URLs; review source URLs and destination cards before allowing an agent to attach files., Use `TRELLO_ALLOWED_WORKSPACES` to limit workspace access, especially when a token can see personal, client, or production boards., Require confirmation before creating boards, adding attachments, deleting or archiving cards, changing due dates, moving cards between lists, or posting comments on behalf of a user.
Privacy notes
Trello API keys, tokens, board IDs, workspace IDs, card IDs, member names, labels, comments, checklists, attachments, due dates, and activity logs can be exposed to the MCP client., Active board and workspace selections may persist locally in Trello MCP configuration., Card descriptions, comments, attachments, and activity histories can contain private customer, roadmap, incident, or operational data., Proxy settings, Trello credentials, and workspace allowlists should be kept out of shared MCP configs, logs, screenshots, and transcripts., Response previews reduce some large card-description exposure, but full-card and activity tools can still return sensitive Trello content.
Author
Jarad DeLorenzo
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
5 safety and 5 privacy notes across 5 risk areas. Review closely: credentials & tokens.
5 areas
SafetyCredentials & tokensTrello MCP Server can create, read, update, move, archive, and delete board data depending on token permissions and requested tools.
SafetyGeneralCard, checklist, label, due-date, start-date, comment, attachment, board, list, workspace, and active-board changes can affect real team workflows.
SafetyLocal filesFile attachments are added from URLs; review source URLs and destination cards before allowing an agent to attach files.
SafetyCredentials & tokensUse `TRELLO_ALLOWED_WORKSPACES` to limit workspace access, especially when a token can see personal, client, or production boards.
SafetyGeneralRequire confirmation before creating boards, adding attachments, deleting or archiving cards, changing due dates, moving cards between lists, or posting comments on behalf of a user.
PrivacyCredentials & tokensTrello API keys, tokens, board IDs, workspace IDs, card IDs, member names, labels, comments, checklists, attachments, due dates, and activity logs can be exposed to the MCP client.
PrivacyData retentionActive board and workspace selections may persist locally in Trello MCP configuration.
PrivacyExecution & processesCard descriptions, comments, attachments, and activity histories can contain private customer, roadmap, incident, or operational data.
PrivacyCredentials & tokensProxy settings, Trello credentials, and workspace allowlists should be kept out of shared MCP configs, logs, screenshots, and transcripts.
PrivacyExecution & processesResponse previews reduce some large card-description exposure, but full-card and activity tools can still return sensitive Trello content.
Disclosure: Community-maintained MIT MCP server for the Trello API. Trello is an Atlassian product; users must follow Trello and workspace access policies when connecting an API token.
Safety notes
Trello MCP Server can create, read, update, move, archive, and delete board data depending on token permissions and requested tools.
Card, checklist, label, due-date, start-date, comment, attachment, board, list, workspace, and active-board changes can affect real team workflows.
File attachments are added from URLs; review source URLs and destination cards before allowing an agent to attach files.
Use `TRELLO_ALLOWED_WORKSPACES` to limit workspace access, especially when a token can see personal, client, or production boards.
Require confirmation before creating boards, adding attachments, deleting or archiving cards, changing due dates, moving cards between lists, or posting comments on behalf of a user.
Privacy notes
Trello API keys, tokens, board IDs, workspace IDs, card IDs, member names, labels, comments, checklists, attachments, due dates, and activity logs can be exposed to the MCP client.
Active board and workspace selections may persist locally in Trello MCP configuration.
Card descriptions, comments, attachments, and activity histories can contain private customer, roadmap, incident, or operational data.
Proxy settings, Trello credentials, and workspace allowlists should be kept out of shared MCP configs, logs, screenshots, and transcripts.
Response previews reduce some large card-description exposure, but full-card and activity tools can still return sensitive Trello content.
Prerequisites
Trello API key and token with access to the boards and workspaces Claude may use.
Bun-compatible published package runtime or an MCP client that can launch the packaged stdio server through npx.
Optional `TRELLO_BOARD_ID` or `TRELLO_WORKSPACE_ID` when a default board or workspace should be selected at startup.
Optional `TRELLO_ALLOWED_WORKSPACES` to constrain the token to specific approved Trello workspaces.
Review of which boards, lists, cards, labels, comments, checklists, attachments, members, and workspace actions the token can read or change.
Schema details
Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
15 minutes
Difficulty
intermediate
Tool listing metadata
Disclosure
Community-maintained MIT MCP server for the Trello API. Trello is an Atlassian product; users must follow Trello and workspace access policies when connecting an API token.
Trello MCP Server connects Claude and other MCP clients to Trello boards through
the Trello API. It provides tools for cards, lists, board activity, comments,
checklists, attachments, labels, workspace selection, board selection, and
health checks while respecting Trello API rate limits.
Use it when Claude needs supervised access to Trello planning, triage,
operations, product, support, or kanban workflows.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, npm metadata, license, package metadata, server entrypoint, Trello API
client, health endpoints, skill instructions, and setup reference for current
setup and behavior details.
Features
List boards, workspaces, lists, cards, comments, checklists, labels, and
board activity.
Create cards, update card details, move cards, manage due dates and start
dates, and work with labels.
Add, update, delete, and retrieve comments on Trello cards.
Fetch complete card data including checklists, attachments, labels, members,
comments, and markdown-formatted output.
Add file attachments from URLs.
Switch active boards and workspaces without restarting the MCP server.
Restrict accessible workspaces with TRELLO_ALLOWED_WORKSPACES.
Use built-in Trello API rate-limit handling and health endpoints.
Installation
Create a Trello API key and token, then configure the MCP server with the
credentials and any desired workspace restrictions:
Create cards from meeting notes or support follow-ups.
Update due dates, labels, comments, and checklist items after review.
Find cards by list, label, name, due date, or board context.
Export card data as markdown for reports or handoffs.
Limit an assistant to specific Trello workspaces for safer operational use.
Safety and Privacy
Trello MCP Server acts through a real Trello API token. Scope the token and
workspace allowlist tightly, keep destructive operations behind confirmation,
and test workflows on non-production boards before using Claude on shared team
boards.
Treat Trello board names, card descriptions, comments, attachments, labels,
checklists, members, due dates, activity logs, API keys, tokens, board IDs, and
workspace IDs as sensitive operational data. Avoid placing credentials or
private card content in shared prompts, logs, screenshots, or public examples.
Show that Trello MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/trello-mcp-server)
How it compares
Trello MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
MCP server for Trello boards, cards, lists, comments, checklists, attachments, labels, board activity, workspace selection, and rate-limited Trello API automation from Claude.
MCP server for Todoist task and project management, with tools for tasks, subtasks, projects, sections, labels, comments, reminders, filters, activity, backups, collaboration, bulk operations, and dry-run testing.
MCP server for Anki flashcards that lets Claude review cards, manage decks, create and update notes, handle tags and media, inspect stats, and drive Anki desktop GUI workflows.
✓Trello MCP Server can create, read, update, move, archive, and delete board data depending on token permissions and requested tools.
Card, checklist, label, due-date, start-date, comment, attachment, board, list, workspace, and active-board changes can affect real team workflows.
File attachments are added from URLs; review source URLs and destination cards before allowing an agent to attach files.
Use `TRELLO_ALLOWED_WORKSPACES` to limit workspace access, especially when a token can see personal, client, or production boards.
Require confirmation before creating boards, adding attachments, deleting or archiving cards, changing due dates, moving cards between lists, or posting comments on behalf of a user.
✓Todoist MCP Server can create, update, delete, complete, reopen, reorder, archive, and bulk-modify tasks, subtasks, projects, sections, labels, comments, reminders, filters, shared labels, and collaboration state.
Bulk create, bulk update, bulk delete, bulk complete, project deletion, section deletion, label deletion, reminder changes, and duplicate merge operations can alter many Todoist records at once.
Dry-run mode simulates mutation operations but still queries real Todoist data for validation.
Pro and Business features such as reminders, filters, shared labels, collaboration, backups, and workspace operations may expose or modify team data.
Require confirmation before deleting tasks or projects, changing due dates in bulk, completing groups of tasks, modifying shared projects, creating reminders, downloading backups, or changing collaboration state.
✓Memory Bank MCP can read, create, and update files inside the configured memory-bank root.
Do not point `MEMORY_BANK_ROOT` at a home directory, source repository root, cloud-sync folder, or any directory containing secrets.
Avoid auto-approving write and update tools until the expected file structure and naming rules are established.
The path validator rejects path traversal and slash-containing file/project names, but users should still keep the root directory narrow and dedicated.
Docker mode requires a bind mount for the memory bank; review the host path and container path before granting write access.
✓Anki MCP Server can create, update, delete, move, tag, rate, and sync cards and notes through AnkiConnect.
Destructive tools include note deletion, media deletion, unused-tag clearing, deck moves, tag replacement, model styling changes, and review rating actions that affect scheduling.
The server supports read-only mode that blocks exposed write actions, but users should still review tool calls before enabling unrestricted study or collection-management workflows.
Media tools can store files from local paths, URLs, or base64 data and can retrieve media as base64 content.
GUI tools can open Anki windows, select cards, edit notes, show answers, and undo the last Anki action.
Remote tunnel or ngrok-style setups expose local Anki to cloud-hosted AI clients and require careful authentication, origin, and URL-sharing controls.
Privacy notes
✓Trello API keys, tokens, board IDs, workspace IDs, card IDs, member names, labels, comments, checklists, attachments, due dates, and activity logs can be exposed to the MCP client.
Active board and workspace selections may persist locally in Trello MCP configuration.
Card descriptions, comments, attachments, and activity histories can contain private customer, roadmap, incident, or operational data.
Proxy settings, Trello credentials, and workspace allowlists should be kept out of shared MCP configs, logs, screenshots, and transcripts.
Response previews reduce some large card-description exposure, but full-card and activity tools can still return sensitive Trello content.
✓Todoist API tokens, task IDs, project IDs, section IDs, label IDs, reminder IDs, comment IDs, user IDs, collaborator details, activity logs, completed tasks, backups, and productivity statistics can be exposed to the MCP client.
Task names, descriptions, comments, due dates, deadlines, labels, reminders, attachments, project notes, and completed-task history can contain private work or personal planning data.
Bulk and filter tools may reveal larger slices of a Todoist workspace than a single-task request.
Backup download tools can expose a broad historical snapshot of Todoist data.
Keep Todoist tokens in local MCP configuration only, and avoid sharing MCP logs, dry-run traces, or transcripts that include private task or project data.
✓Memory-bank files can contain project plans, architecture notes, decisions, credentials accidentally pasted into notes, customer context, meeting details, or personal information.
Tool calls may expose project names, file names, memory contents, root-path assumptions, and update text to the MCP client and model provider.
Multi-project listing can reveal all projects stored under the memory-bank root.
Auto-approved memory tools can persist model-generated statements as project memory without human review.
Back up important memory-bank directories and review retention expectations before sharing them across clients or machines.
✓Tool calls can expose deck names, note fields, card contents, tags, review history, media filenames, base64 media, selected notes, collection stats, scheduling metadata, and AnkiConnect errors.
Flashcards may contain medical, language-learning, school, work, personal, customer, or confidential study material.
Sync can send Anki collection changes to AnkiWeb according to the user's Anki account and sync settings.
Local media file paths, URLs imported into cards, and GUI-selected note IDs can enter MCP client context and model logs.
Remote tunnel providers and hosted clients may process connection metadata or traffic according to their own policies.
Prerequisites
Trello API key and token with access to the boards and workspaces Claude may use.
Bun-compatible published package runtime or an MCP client that can launch the packaged stdio server through npx.
Optional `TRELLO_BOARD_ID` or `TRELLO_WORKSPACE_ID` when a default board or workspace should be selected at startup.
Optional `TRELLO_ALLOWED_WORKSPACES` to constrain the token to specific approved Trello workspaces.
Todoist API token from Todoist integrations developer settings.
Node.js 18 or newer for the npm stdio server.
Review of whether the token has access to personal, shared, Pro, Business, or workspace features.
Optional `DRYRUN=true` for simulating mutation tools while still validating against real Todoist data.
Node.js and npm available for `npx`.
A dedicated memory-bank root directory, separate from source repositories and secrets.
Project-specific subdirectories created under `MEMORY_BANK_ROOT`.
MCP client approval rules reviewed before allowing write or update operations.
Anki Desktop installed and running.
The AnkiConnect add-on installed in Anki.
Node.js 22.12 or newer for the npm package path.
Review of which decks, cards, tags, media files, and note types the MCP client may access.