Skip to main content
Book a demo

Connect Sigma to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Sigma

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

  4. 4

    Use Sigma from GitHub Copilot

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

Tools

7 Sigma tools in GitHub Copilot

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

  • Begin session

    REQUIRED — You MUST call this tool before using any other Sigma tool in a conversation.

  • Call agent

    Call a Sigma workbook agent with a message or conversation.

  • Describe

    Inspect the schema of a Sigma data source.

  • List documents

    Browse a named document collection in the Sigma workspace.

  • List workbook agents

    List the workbook agents you can edit across your organization

  • Query

    Execute a SQL query against a Sigma data source and return the results.

  • Search

    Search across the entire Sigma workspace to discover workbooks, data models, data model elements, and tables.

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