Skip to main content
Book a demo

Connect Harmonic to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

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

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

Tools

47 Harmonic tools in GitHub Copilot

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

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

  • Gateway policy (available)

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