Skip to main content
Back to the Ramp MCP server

MCP Gateway · Claude Code

Ramp icon

Connect Ramp to Claude Code

Engineering teams pay for cloud services, SaaS seats and API usage through Ramp, and the numbers matter when you choose what to build on. Claude Code can read Ramp's financial data for spend analysis through the Speakeasy MCP Gateway. Hooks check each prompt and tool call before Claude Code runs it, and its OpenTelemetry exporter ties the session to you.

Category
Sales & CRM
Authentication
OAuth
Claude Code
CLI

Behind the MCP Gateway

Run Ramp MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Ramp call inspected and logged.

Deploy on MCP Gateway

Set up

Add Ramp to Claude Code in 4 steps

  1. 01

    Add Ramp from the catalog

    An admin finds Ramp in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.

    Ramp uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.

    Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.

  2. 02

    Choose who can use Ramp

    Give teams the mcp:connect scope on the Ramp server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Ramp to their gateway on the next call, and removing it takes it away.

  3. 03

    Connect Claude Code

    Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.

    Run the command below with your organization gateway URL.

    Open /mcp in Claude Code and choose Authenticate to sign in.

    claude mcp add --transport http --scope user \
      'speakeasy' \
      'https://<organization host>/mcp/gateway/<organization slug>'
  4. 04

    Sign in and use Ramp from Claude Code

    The first time Claude Code connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Ramp needs its own OAuth grant, so each person connects it once. Until they do, Ramp calls fail while the rest of the gateway keeps working.

    From then on, Ramp's tools appear in Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.

To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.

Use cases

What Claude Code users do with Ramp

Check vendor spend before adding a dependency

Before you adopt a paid API in your code, ask Claude Code what the company already spends with that vendor and whether another team pays for something similar.

Script a recurring spend report

Have Claude Code read Ramp spend data for your team's tools and write a small script or notebook that turns it into the monthly cost table your manager asks for.

Explain a jump in infrastructure costs

When a cloud bill spikes, pull the relevant Ramp spend and compare it with recent changes in the repository to find which deploy caused it.

Control

What Speakeasy can see and stop in Claude Code

The gateway covers every client the same way. The rest depends on what Claude Code exposes to Speakeasy.

Tool logs

Gateway

Every Ramp call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Ramp tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Ramp can reject a tool request before it reaches the server, or withhold a result from Claude Code. MCP-scoped policies are enabled per organization.

Prompt and tool-call blocking

Claude Code

Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.

User attribution

Claude Code

Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.

Budgets

Claude Code

Spend limits can block Claude Code traffic once a budget is reached.

Device agent and MDM

Claude Code

The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.

Anthropic inference hooks

Claude Code

On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).

  • Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
  • Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.

Questions

Frequently asked questions

Should developers have Ramp access in Claude Code at all?
That's your choice. You decide which Ramp tools each team can call at the MCP Gateway, so engineering can get the spend views it needs while finance keeps broader access.
Can spend from Claude Code itself be capped?
Yes. Budgets set spend limits that can block Claude Code traffic once a budget is reached.
How do Claude Code users get Ramp?
An admin adds Ramp from the Speakeasy MCP Catalog and grants access by team or role. Add the organization gateway as an HTTP MCP server, then authenticate from /mcp. Each person then sees only the Ramp tools their access allows.
Are Ramp calls from Claude Code logged?
Yes. Ramp calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Ramp in other clients

AI everywhere.

Control here.