Skip to main content
Book a demo

Connect Vantage to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

    Add Vantage to Runlayer

    Vantage isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Cline CLI to Runlayer

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

    Cline CLI setup guide
  3. 3

    Sign in to Vantage

    Sign in the way Vantage requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Vantage from Cline CLI

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

Tools

157 Vantage tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call.

  • Add team member

    Add a user to a Team by email address and assign their Team role.

  • Create access policy

    Create an Access Policy, which limits the costs visible to the Teams it is assigned to.

  • Create annotation

    Create an Annotation on one or more Cost Reports for a specific date.

  • Create billing rule

    Exclusion rules require charge_type.

  • Create budget

    Creates a budget based on the parameters specified.

  • Create budget alert

    Create a Budget Alert that notifies users or connected channels when one or more Budgets reach a percentage threshold during a monthly time window.

  • Create canvas

    Creates a Canvas based on the parameters specified.

  • Create cost alert

    Create a new Cost Alert in Vantage.

See all 157 Vantage 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 Vantage 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