Skip to main content
Book a demo

Connect Serval to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Serval

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

  4. 4

    Use Serval from GitHub Copilot

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

Tools

402 Serval tools in GitHub Copilot

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

  • Add entity type field

    Deprecated: use POST /v2/entity-type-fields.

  • Add label to app instance

    DEPRECATED: use AddTagToSubject.

  • Add tag to subject

    Attach a tag to a subject (resource, role, app instance, workflow, or guidance).

  • Add ticket assignment group

    Add a group to the team's configured assignment groups.

  • Add ticket relevant asset

    Add a relevant asset to a ticket.

  • Aggregate entities

    Aggregate live-entity counts for one entity schema (database), grouped by entity type or by creation-time bucket (day or month).

  • Archive entity

    Archive an entity, hiding it from active browse while keeping its key reserved so the key cannot be reused.

  • Archive ticket

    Move a ticket into cold storage, removing it from most views.

See all 402 Serval 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 Serval 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