Skip to main content
Back to the Ramp MCP server

MCP Gateway · OpenCode

Ramp icon

Connect Ramp to OpenCode

Terminal-first developers can ask OpenCode about Ramp spend as easily as they grep logs. Speakeasy reviews every prompt and Ramp request through the plugin before anything executes, and the same plugin reports token and cost totals per turn, so the agent's own usage is visible next to the company's.

Category
Sales & CRM
Authentication
OAuth
OpenCode
Terminal

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

    Add the server to OpenCode's own mcp config block as a remote server.

    Copy the server's URL from its hosted install page in Speakeasy.

    Add it to the mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Ramp from OpenCode

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

OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.

Use cases

What OpenCode users do with Ramp

Answer a quick spend question

Ask OpenCode how much the team spent on a particular cloud provider last month without opening the Ramp dashboard or waiting for finance.

Export spend for a cost model

Read Ramp spend for the services in a project and have OpenCode write it to a CSV that your capacity planning model can load.

Compare agent costs with vendor spend

Put the token and cost totals the plugin reports next to Ramp spend on AI vendors to see how much of the bill comes from coding agents.

Control

What Speakeasy can see and stop in OpenCode

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

Prompt and tool-call blocking

OpenCode

The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.

Usage telemetry

OpenCode

Token and cost totals flow through the plugin, reported per turn.

Device agent

OpenCode

The device agent installs and maintains the observability package.

  • OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
  • Tool output is blocked at the gateway rather than in OpenCode's hooks.

Questions

Frequently asked questions

How is Ramp added to OpenCode?
Add the server's URL from its hosted install page to the mcp block of your OpenCode config with type set to remote, then restart OpenCode and sign in when prompted.
Is sensitive financial data redacted?
PII redaction and prompt injection detection run on every Ramp tool call at the gateway, and each call lands in one audit log tied to a named employee, exportable to your SIEM.
How do OpenCode users get Ramp?
An admin adds Ramp from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Ramp tools their access allows.
Are Ramp calls from OpenCode 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.