Skip to main content
Book a demo

Connect Mintlify to GitHub Copilot

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

Book a demo GitHub Copilot setup guide

Set up

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

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

    GitHub Copilot setup guide
  3. 3

    Sign in to Mintlify

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

  4. 4

    Use Mintlify from GitHub Copilot

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

Tools

35 Mintlify tools in GitHub Copilot

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

  • Agent review settings

    Change whether agent edits push directly to the deploy branch (push_to_main) or open a pull request (create_pull_request).

  • Checkout

    Select a deployment and open its editor session in one call.

  • Create node

    Insert a node into the navigation tree under parentId (null = root).

  • Delete node

    Remove a node and its subtree from the navigation tree by nodeId.

  • Diff

    Returns the list of changes between current session and main.

  • Discard session

    End the session without creating a PR.

  • Edit page

    String-replace edit on a page Y.

  • Execute code

    Run TypeScript/JavaScript against the Admin MCP dashboard SDK inside a sandboxed Cloudflare isolate.

See all 35 Mintlify 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 Mintlify 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