Skip to main content

Connect Vantage to Claude

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

Set up

Add Vantage to Claude in four steps

Admins approve the server once. Everyone in Claude 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 to Runlayer

    Admins install the Runlayer Plugin for everyone from Claude’s admin plugin settings, or users add it themselves. With direct tool listing turned on for your deployment, Vantage’s 157 tools show up in Claude’s own tool list.

    Claude 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

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

Tools

157 Vantage tools in Claude

Runlayer policy decides which of these Claude 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

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

  • Gateway policy (available)

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

  • Audit trail (available)

    Each call is recorded with the user, Claude as the client, the tool, and the policy and scanner decisions.

  • Anthropic inference hooks (available)

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

  • Compliance API import (available)

    Anthropic Compliance API imports Claude web and desktop chats for review.

  • Managed browser extension (available)

    Managed Chrome, Edge, and Firefox deployments can monitor supported web-chat activity and apply prompt-time controls where the surface permits it.

  • Stop a call before it runs (available)

    Runlayer can reject a Claude 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)

    Anthropic Inference hooks cannot return a rewritten prompt, so Runlayer cannot mask content in Claude. The gateway still applies policy to the call.

Frequently asked questions

Connect more

Find another combination