Skip to main content
Book a demo

Connect Ramp to Claude Code

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

Book a demo Claude Code setup guide

Set up

Add Ramp 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

    Approve Ramp in Runlayer

    Add Ramp from the catalog and choose who can use it and which of its tools are allowed.

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

    Claude Code setup guide
  3. 3

    Sign in to Ramp

    Each user signs in to Ramp with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use Ramp from Claude Code

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

Tools

124 Ramp tools in Claude Code

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

  • Activate card

    Activate a card by its last four digits.

  • Add traveler loyalty program

    Compatibility route for callers that have not migrated to SetTravelerLoyaltyProgram.

  • Answer policy question

    Get an answer to a question about the expense policy or funds (amount, restrictions, etc).

  • Approve or reject bill

    Approve or reject a submitted bill that is pending approval.

  • Approve or reject reimbursement

    Approve or reject an employee reimbursement request for an out-of-pocket expense.

  • Approve or reject request

    Approve or reject a pending unified request for spend allocation (fund), purchase order, or procurement approval.

  • Approve or reject transaction

    Approve or reject a transaction awaiting your review.

  • Cancel reimbursement payment

    Cancel the payment on a reimbursement that has been approved but not yet paid out.

See all 124 Ramp 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 Ramp 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