Skip to main content
Book a demo

Connect Vantage to Cursor

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

Book a demo Cursor setup guide

Set up

Add Vantage to Cursor in four steps

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

    Runlayer’s CLI installs the Runlayer Plugin natively in Cursor, and admins can roll it out org-wide with Auto Sync plus a Cursor team rule. With direct tool listing turned on for your deployment, Vantage’s 157 tools show up in Cursor’s own tool list.

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

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

Tools

157 Vantage tools in Cursor

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

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

  • Gateway policy (available)

    Every Vantage call from Cursor passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cursor 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 Cursor runs it, including calls to MCP servers.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before Cursor’s model sees it.

  • Redact output in place (not available)

    Cursor cannot take masked output, so Runlayer can block a tool’s output but not mask it. The gateway still applies policy to the call.

In Cursor

  • Runlayer cannot tell Agents Window sessions apart from regular IDE sessions.
  • The Cursor CLI sends fewer session events than the IDE, but Runlayer’s allow and deny decisions still apply.

Frequently asked questions

Connect more

Find another combination