Skip to main content
Back to the Ramp MCP server

MCP Gateway · Claude

Ramp icon

Connect Ramp to Claude

Finance teams and budget owners can ask Claude spend questions in plain language and get answers from Ramp data. Claude reads the financial data through the Speakeasy MCP Gateway, so nobody shares a Ramp login, and each person only sees the servers their role can reach.

Category
Sales & CRM
Authentication
OAuth
Claude
Web, desktop and mobile

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

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Ramp from Claude

    The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Ramp

Explain a department's monthly spend

Ask Claude where a department's money went last month, broken down by vendor and category, and get a summary ready for the budget meeting.

Find duplicate software subscriptions

Have Claude read software spend across teams and point out vendors that several departments pay for separately, so procurement can consolidate them.

Draft a variance note

When actual spend misses the forecast, Claude compares the Ramp figures with your plan and drafts a short note explaining the biggest differences.

Control

What Speakeasy can see and stop in Claude

The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can Claude block a prompt that asks for Ramp data?
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Do budgets apply to Claude usage with Ramp?
No. Budgets don't cover Claude web and desktop usage. Every Ramp tool call is still logged against a named employee.
How do Claude users get Ramp?
An admin adds Ramp from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Ramp tools their access allows.
Are Ramp calls from Claude 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.