Skip to main content
Book a demo

Connect Gem to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

    Add Gem to Runlayer

    Gem isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect GitHub Copilot to Runlayer

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Gem

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

  4. 4

    Use Gem from GitHub Copilot

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

Tools

15 Gem tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call.

  • Get application

    Look up one application (a candidate on a specific job) by ext_id — status, stage, stage_entry, gem_status (the Talent Pipeline's computed next-step status and SLA health, e.g. NEEDS_DECISION /…

  • Get job

    Look up one job by ext_id — title, status, requisition id, ATS, department/office, and link.

  • Get metrics catalog

    List the metrics and dimensions this team can report on with query_metrics.

  • Get person

    Look up one candidate by ext_id — name, current title, company, school, emails, phone numbers, and links, plus optional fields (full work history, education, custom fields, applications, activity…

  • Get project

    Look up one project by ext_id — name, description, owner, link, type, privacy, archived status, and people_count (candidates in the project).

  • Get saved report

    Look up one saved analytics report (Pipeline Analytics or Outreach) by ext_id — its name, type, owner, link, and a ready-to-run query_metrics payload translated from the report's saved configuration.

  • Get sequence

    Look up one outreach sequence by ext_id — name, status, whether it is a reusable template (is_template) and whether it is archived (is_archived), owner, link, a version (the sequence's edit version —…

  • Get sequence tokens

    List the merge tokens available for writing a sequence stage's subject or body on this team.

See all 15 Gem 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 Gem 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