Skip to main content
Book a demo

Connect Profound to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

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

    Profound 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 Profound’s 61 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 Profound

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

  4. 4

    Use Profound from GitHub Copilot CLI

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

Tools

61 Profound tools in GitHub Copilot CLI

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

  • Add knowledge base document

    Add ONE new document (inline markdown text) to a knowledge base.

  • Archive project

    Preview or archive (retire) a project — set it aside without deleting it.

  • Create agent definition

    Create a draft agent definition — preview first, then apply on confirmation.

  • Create doc

    Create a new document in the Profound platform from content you have written.

  • Create project task

    Preview or add a task ("play") to a project.

  • Create prompts

    Create one or more prompts in a category.

  • Get agent

    Get details of an agent, including its input_schema.

  • Get agent definition

    Read back an agent's full workflow graph so you can copy and edit it.

See all 61 Profound 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 Profound 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