Connect Metaview to GitHub Copilot CLI
Give GitHub Copilot CLI 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 CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 1
Approve Metaview in Runlayer
Add Metaview from the catalog and choose who can use it and which of its tools are allowed.
- 2
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Metaview’s 53 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 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
Use Metaview from GitHub Copilot CLI
Metaview’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
53 Metaview tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot 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…
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Metaview call from GitHub Copilot CLI 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 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 or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more