Skip to main content
Book a demo

Connect Ramp to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Ramp to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI 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 Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Ramp’s 124 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

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

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

Tools

124 Ramp tools in Cline CLI

Runlayer policy decides which of these Cline CLI 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 Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Ramp call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline CLI 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.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination