Skip to main content
Book a demo

Connect Navattic to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Navattic

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

  4. 4

    Use Navattic from GitHub Copilot

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

Tools

62 Navattic tools in GitHub Copilot

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

  • Create brain asset

    Add a URL, FILE, or TEXT asset to an agent's brain.

  • Create launchpad share link

    Create a launchpad share link, sourced from either a set of custom flows or a demo.

  • Delete brain asset

    Permanently delete a Brain asset.

  • Get account

    Get a detailed profile for a specific company account by ID.

  • Get agent demo

    Get a Navattic agent's configuration — objective, personality, tone, FAQs, pronunciations, CTA, welcome screen, language, voice, avatar, escalation/interruption flags, and the linked environment.

  • Get agent demo session

    Get full details for a Navattic agent session: parsed transcript turns, qualifications, summary, sentiment, signals detected, outcome reached, status, end user, and the Steel session viewer URL for…

  • Get agent environment

    Get an agent environment and its folder/flow tree.

  • Get demo

    Get a specific demo.

See all 62 Navattic 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 Navattic 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