Skip to main content

Connect Vantage to Claude Code

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

Set up

Add Vantage 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 Vantage to Runlayer

    Vantage 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, Vantage’s 157 tools show up in Claude Code’s own tool list (supported Claude Code versions).

    Claude Code setup guide
  3. 3

    Sign in to Vantage

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

  4. 4

    Use Vantage from Claude Code

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

Tools

157 Vantage tools in Claude Code

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

  • Add team member

    Add a user to a Team by email address and assign their Team role.

  • Create access policy

    Create an Access Policy, which limits the costs visible to the Teams it is assigned to.

  • Create annotation

    Create an Annotation on one or more Cost Reports for a specific date.

  • Create billing rule

    Exclusion rules require charge_type.

  • Create budget

    Creates a budget based on the parameters specified.

  • Create budget alert

    Create a Budget Alert that notifies users or connected channels when one or more Budgets reach a percentage threshold during a monthly time window.

  • Create canvas

    Creates a Canvas based on the parameters specified.

  • Create cost alert

    Create a new Cost Alert in Vantage.

See all 157 Vantage tools

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 Vantage 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