Skip to main content
Book a demo

Connect Plaid to Claude Code

Give Claude Code governed access to Plaid’s 5 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Code setup guide

Set up

Add Plaid to Claude Code in four steps

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

  1. 1

    Add Plaid to Runlayer

    Plaid isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Claude Code to Runlayer

    Runlayer’s CLI installs the Runlayer Plugin natively in Claude Code, and an Anthropic org install also reaches Claude Code. With direct tool listing turned on for your deployment, Plaid’s 5 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to Plaid

    Sign in the way Plaid requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Plaid from Claude Code

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

Tools

5 Plaid tools in Claude Code

Runlayer policy decides which of these Claude Code users can call.

  • Debug item

    Diagnose a Plaid item by retrieving its state information.

  • Get link analytics

    Retrieves Plaid Link analytics data for analyzing user conversion and error rates.

  • Get tools introduction

    Returns a list of all available tools with a brief introduction for each.

  • Get usages

    Retrieves usage metrics for Plaid products and services.

  • List teams

    Retrieve teams associated with the user and present them as a selectable list.

Control

What Runlayer can see and stop in Claude Code

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Claude 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.

  • Anthropic inference hooks (available)

    With Claude Enterprise, Anthropic sends each governed Claude Code prompt to Runlayer before inference, with nothing installed on devices (Anthropic beta).

  • OTLP telemetry (available)

    Claude Code can export OpenTelemetry logs to Runlayer for observe-only session reconstruction.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Claude Code runs it.

  • Block output after it runs (available)

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

  • Redact output in place (available)

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

In Claude Code

  • When a tool fails, Runlayer records the error but cannot hide it.

Frequently asked questions

Connect more

Find another combination