Connect Omni to Claude Cowork
Give Claude Cowork governed access to Omni’s 25 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Omni 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 Omni to Runlayer
Omni 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, Omni’s 25 tools show up in Claude Cowork’s own tool list.
Claude Cowork setup guide - 3
Sign in to Omni
Sign in the way Omni requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Omni from Claude Cowork
Omni’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.
Tools
25 Omni tools in Claude Cowork
Runlayer policy decides which of these Claude Cowork users can call.
Ask Omni
Starts the full Omni AI agent on an open-ended or multi-step analytical question and returns immediately with a 'jobId' — it does NOT wait for or return the answer, which is retrieved separately once…
Cancel job
Stops a job started by askOmni.
Check dashboard download
Polls a dashboard download started by startDashboardDownload.
Check status
Checks on a job started by askOmni and returns quickly.
Fetch dashboard download
Returns the png a completed dashboard download produced — the job from startDashboardDownload once checkDashboardDownload reports it "complete" — as an image you can look at, after a text block with…
Get app
Alpha — the app content shape may change without a deprecation cycle.
Get app draft
Alpha — the app content shape may change without a deprecation cycle.
Get data
Gets data by generating and executing a query from natural language.
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 Omni 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