Connect Trello to Codex
Give Codex governed access to Trello’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Trello to Codex in four steps
Admins approve the server once. Everyone in Codex 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 Codex to Runlayer
Runlayer’s CLI adds the Runlayer Plugin to Codex’s local plugin marketplace, and users then enable it in Codex. With direct tool listing turned on for your deployment, Trello’s 15 tools show up in Codex’s own tool list (Codex 0.122 or newer, installed through the Runlayer CLI).
Codex 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 Codex
Trello’s approved tools appear in Codex. Every call is checked against policy and recorded.
Tools
15 Trello tools in Codex
Runlayer policy decides which of these Codex 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 Codex
Some controls apply to every client at the gateway. Others depend on what Codex exposes to Runlayer.
Gateway policy (available)
Every Trello call from Codex passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Codex as the client, the tool, and the policy and scanner decisions.
Client hooks (available)
Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.
Stop a call before it runs (available)
Runlayer can deny a tool call or permission request before Codex runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before Codex’s model sees it.
Redact output in place (not available)
Codex cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.
Frequently asked questions
Connect more