Skip to main content
Book a demo

Connect Serval to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add Serval to GitHub Copilot CLI in four steps

Admins approve the server once. Everyone in GitHub Copilot CLI 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 CLI to Runlayer

    Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Serval’s 402 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    GitHub Copilot CLI 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 CLI

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

Tools

402 Serval tools in GitHub Copilot CLI

Runlayer policy decides which of these GitHub Copilot CLI 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 CLI

Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Serval call from GitHub Copilot CLI 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 CLI as the client, the tool, and the policy and scanner decisions.

  • Client hooks (available)

    Capture supported prompts, reasoning, local and MCP tool calls, responses, and scanner decisions in real time.

  • Stop a call before it runs (available)

    Runlayer can deny a tool call or permission request before GitHub Copilot CLI runs it.

  • Block output after it runs (available)

    Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.

  • Redact output in place (available)

    Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.

In GitHub Copilot CLI

  • When a tool fails, Runlayer records the error but cannot replace it.

Frequently asked questions

Connect more

Find another combination