Skip to main content
Back to the Ramp MCP server

MCP Gateway · Claude Cowork

Ramp icon

Connect Ramp to Claude Cowork

Month-end close and budget planning involve reading a lot of spend data and writing it up carefully. Cowork can work through Ramp data as a longer task and produce the finished analysis. Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs, and Cowork's OTLP export ties the work to a person.

Category
Sales & CRM
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork connects to the Ramp server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Ramp from Claude Cowork

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

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Ramp

Build next year's budget baseline

Cowork reads twelve months of Ramp spend, groups it by department and vendor, and writes a baseline spreadsheet with notes on one-off costs to exclude.

Review spend for month-end close

Go through the month's Ramp spend category by category, flag anything unusual for a finance lead, and draft the commentary that goes with the close pack.

Audit software vendors company-wide

Cowork lists every software vendor in Ramp spend, totals each one, and produces a renewal calendar document with owners to confirm.

Control

What Speakeasy can see and stop in Claude Cowork

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

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Can the device agent enforce Ramp settings in Cowork?
No. Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies: the synced plugin marketplace and Cowork's monitoring settings.
Can Cowork prompts about Ramp be checked before inference?
On Claude Enterprise, prompts can be checked before inference (beta). Agent hooks also send each prompt to Speakeasy before the step runs.
How do Claude Cowork users get Ramp?
An admin adds Ramp from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Ramp tools their access allows.
Are Ramp calls from Claude Cowork 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.