Skip to main content
Book a demo

Connect Metaview to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

    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 Cline CLI to Runlayer

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

    Cline CLI 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 Cline CLI

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

Tools

53 Metaview tools in Cline CLI

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

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

  • Gateway policy (available)

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