Connect Trello to Claude Cowork
Give Claude Cowork governed access to Trello’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Trello to Claude Cowork in four steps
Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.
- 1
Add Trello to Runlayer
Trello isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.
Adding a connector manually - 2
Connect Claude Cowork to Runlayer
Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Trello’s 15 tools show up in Claude Cowork’s own tool list.
Claude Cowork setup guide - 3
Sign in to Trello
Sign in the way Trello requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Trello from Claude Cowork
Trello’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.
Tools
15 Trello tools in Claude Cowork
Runlayer policy decides which of these Claude Cowork users can call.
Read board
Read Trello boards.
Read card
Fetch a single card by id or card URL (cardIdOrUrl required).
Read checklist
Read Trello checklists (and their check items) attached to a card.
Read inbox
Triage and review the authenticated user's Trello Inbox — the personal quick-capture board where new cards and notifications land.
Read list
Read Trello lists.
Read member
Get a Trello member's profile.
Read planner
Read Trello Planner information for the authenticated user.
Read workspace
Read Trello workspaces (organizations) the current user has access to.
Control
What Runlayer can see and stop in Claude Cowork
Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.
Gateway policy (available)
Every Trello call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.
OTLP telemetry (available)
Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Stop a call before it runs (available)
Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.
In Claude Cowork
- Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.
Frequently asked questions
Connect more