Skip to main content
Book a demo

Connect Metabase to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

Add Metabase 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 Metabase in Runlayer

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Metabase

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

  4. 4

    Use Metabase from GitHub Copilot

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

Tools

45 Metabase tools in GitHub Copilot

Runlayer policy decides which of these GitHub Copilot users can call. 25 read data only and 6 can change or delete data.

  • Construct query

    Construct a Metabase query from a structured program with source and operations.

  • Create dashboard

    Create a dashboard in Metabase.

  • Create question

    Save a query as a named question in Metabase.

  • Execute query

    Execute a previously constructed query and return the results with column metadata, row count, and execution time.

  • Get metric

    Get details about a metric including its queryable dimensions.

  • Get metric field values

    Get sample values and statistics for a field in a metric.

  • Get table

    Get details about a table including its fields, related tables, and metrics.

  • Get table field values

    Get sample values and statistics for a field in a table.

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