Skip to main content

Connect Trello to VS Code

Give VS Code governed access to Trello’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Set up

Add Trello to VS Code in four steps

Admins approve the server once. Everyone in VS Code then gets it through the same governed connection.

  1. 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. 2

    Connect VS Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in VS Code; users can also add it over MCP. With direct tool listing turned on for your deployment, Trello’s 15 tools show up in VS Code’s own tool list (VS Code 1.103 or newer).

    VS Code setup guide
  3. 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. 4

    Use Trello from VS Code

    Trello’s approved tools appear in VS Code. Every call is checked against policy and recorded.

Tools

15 Trello tools in VS Code

Runlayer policy decides which of these VS Code 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.

See all 15 Trello tools

Control

What Runlayer can see and stop in VS Code

Some controls apply to every client at the gateway. Others depend on what VS Code exposes to Runlayer.

  • Gateway policy (available)

    Every Trello call from VS Code passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, VS Code 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 before VS Code runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before VS Code’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a tool’s output in VS Code and pass the rest through.

Frequently asked questions

Connect more

Find another combination