Connect Vantage to Claude Cowork
Give Claude Cowork governed access to Vantage’s 157 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Vantage to Claude Cowork in four steps
Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.
- 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
Connect Claude Cowork to Runlayer
Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Vantage’s 157 tools show up in Claude Cowork’s own tool list.
Claude Cowork setup guide - 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
Use Vantage from Claude Cowork
Vantage’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.
Tools
157 Vantage tools in Claude Cowork
Runlayer policy decides which of these Claude Cowork 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.
Control
What Runlayer can see and stop in Claude Cowork
Some controls apply to every client at the gateway. Others depend on what Claude Cowork exposes to Runlayer.
Gateway policy (available)
Every Vantage call from Claude Cowork passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, Claude Cowork as the client, the tool, and the policy and scanner decisions.
Anthropic inference hooks (available)
Anthropic Inference hooks let Runlayer check Claude Cowork prompts before inference.
OTLP telemetry (available)
Claude Cowork can send supported OpenTelemetry events to Runlayer for observe-only session visibility.
Stop a call before it runs (available)
Runlayer can reject a Claude Cowork prompt before Anthropic runs it, which stops the whole request rather than one tool call.
Block output after it runs (available)
Because Runlayer checks the full prompt, tool results in it can be blocked before the model sees them.
Redact output in place (not available)
Runlayer cannot mask content in Claude Cowork. The gateway still applies policy to the call.
In Claude Cowork
- Cowork session data sent over OpenTelemetry is for monitoring only and cannot stop anything.
Frequently asked questions
Connect more
