Skip to main content
Book a demo

Connect Metaview to Claude Cowork

Give Claude Cowork governed access to Metaview’s 53 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Claude Cowork setup guide

Set up

Add Metaview to Claude Cowork in four steps

Admins approve the server once. Everyone in Claude Cowork then gets it through the same governed connection.

  1. 1

    Approve Metaview in Runlayer

    Add Metaview from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect Claude Cowork to Runlayer

    Claude Cowork gets connector tools through the Runlayer Plugin. With direct tool listing turned on for your deployment, Metaview’s 53 tools show up in Claude Cowork’s own tool list.

    Claude Cowork setup guide
  3. 3

    Sign in to Metaview

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

  4. 4

    Use Metaview from Claude Cowork

    Metaview’s approved tools appear in Claude Cowork. Every call is checked against policy and recorded.

Tools

53 Metaview tools in Claude Cowork

Runlayer policy decides which of these Claude Cowork users can call. 11 read data only.

  • Create AI field

    Create a new AI field, or update an existing one (pass field_id).

  • Create report

    Create a new saved report, or update an existing one (pass report_id), in the Metaview web-app.

  • Create snippet

    Save ONE clip of a conversation as a snippet and return links to it.

  • Enrich candidate contacts

    Enrich email addresses or phone numbers for one or more candidates.

  • Fetch candidates

    Look up people/candidates and get, per candidate: profile (professional background — experience, education, skills, location; resolved from a LinkedIn URL, given or found in ATS data) and ats…

  • Find candidate's sequences

    Check if a candidate is enrolled in any sequences — including sequences created by other users.

  • Generate notes

    Generate (or regenerate) AI Notes for a conversation, optionally with a specific built-in or custom template — including to preview how a newly created or updated template renders on a real…

  • Get application review details

    Get the full state of one Application Review: the ACTIVE ICP, any pending DRAFT edit, the RANKING version if a rerank is running, version history, a decision summary, and the fit-band distribution of…

See all 53 Metaview tools

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

Find another combination