Skip to main content
Book a demo

Connect Gumloop to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

    Approve Gumloop in Runlayer

    Add Gumloop from the catalog and choose who can use it and which of its tools are allowed.

  2. 2

    Connect GitHub Copilot to Runlayer

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Gumloop

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

  4. 4

    Use Gumloop from GitHub Copilot

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

Tools

45 Gumloop tools in GitHub Copilot

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

  • List agents

    List agents in your Gumloop account, with optional search and workspace filtering.

  • Get agent

    Fetch a single Gumloop agent's configuration by its ID.

  • Ask gummie

    Ask questions and get AI-powered answers from Gumloop documentation.

  • Attach agent MCP server

    Attach an MCP server (connector) to a Gumloop agent, or update its configuration if already attached.

  • Attach agent skills

    Attach one or more existing skills to a Gumloop agent.

  • Call MCP tool

    Execute a single tool on a connected MCP server.

  • Cancel session

    Cancel an in-progress Gumloop agent session.

  • Create agent

    Create a new Gumloop agent with a name, model, and optional configuration.

See all 45 Gumloop 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 Gumloop 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