Skip to main content
Book a demo

Connect Harmonic to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add Harmonic 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. 1

    Add Harmonic to Runlayer

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

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Harmonic’s 47 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI setup guide
  3. 3

    Sign in to Harmonic

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

  4. 4

    Use Harmonic from GitHub Copilot CLI

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

Tools

47 Harmonic tools in GitHub Copilot CLI

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

  • Add companies to list

    Add companies to an existing company list.

  • Add people to list

    Add people to an existing people list.

  • Create company list

    Create a new company list.

  • Create company list custom field

    Create a custom field (column) for a company list.

  • Create global custom field

    Create a new global custom field for companies or people.

  • Create list

    Create an empty company, person, or investor list in the workspace's shared project.

  • Create list custom field

    Create a custom field on any company, person, or investor list.

  • Create list entries

    Add Harmonic companies, people, or investors to an existing list by creating list entries from their URNs.

See all 47 Harmonic tools

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

Find another combination