Skip to main content

Connect Metaview to GitHub Copilot

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

Set up

Add Metaview to GitHub Copilot in four steps

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

    GitHub Copilot gets connector tools through the Runlayer Plugin, and reaches Metaview’s 53 tools through the plugin’s search and execute tools.

    GitHub Copilot 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 GitHub Copilot

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

Tools

53 Metaview tools in GitHub Copilot

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

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

  • Gateway policy (available)

    Every Metaview call from GitHub Copilot passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, GitHub Copilot as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for GitHub Copilot yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination