Skip to main content
Book a demo

Connect Sumble to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

    Sumble 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 Sumble’s 38 tools through the plugin’s search and execute tools.

    GitHub Copilot setup guide
  3. 3

    Sign in to Sumble

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

  4. 4

    Use Sumble from GitHub Copilot

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

Tools

38 Sumble tools in GitHub Copilot

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

  • Add contacts to list

    Add people to an existing contact list.

  • Add organizations to list

    Add organizations to an existing list.

  • Create contact list

    Create a new contact list (people list).

  • Create organization list

    Create a new organization list.

  • Find match and enrich jobs

    The primary jobs tool: look up jobs by id or search the jobs corpus, and return exactly the attributes you ask for, with optional related people.

  • Find match and enrich organizations

    Find, match, and enrich organizations in one call.

  • Find match and enrich people

    The primary people tool: resolve people and return exactly the attributes you ask for, with optional related people and contact reveals.

  • Find match and enrich teams

    Find the teams inside an organization and return selected attributes, related people, and job postings.

See all 38 Sumble 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 Sumble 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