Skip to main content
Book a demo

Connect Apollo.io to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add Apollo.io 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 Apollo.io to Runlayer

    Apollo.io 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 Apollo.io’s 99 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 Apollo.io

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

  4. 4

    Use Apollo.io from GitHub Copilot CLI

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

Tools

99 Apollo.io tools in GitHub Copilot CLI

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

  • Create accounts bulk

    Create many accounts (companies) in one call.

  • Create accounts

    Use the Create an Account endpoint to add a new account to your team's Apollo account.

  • Update accounts

    Use the Update an Account endpoint to update existing accounts in your team's Apollo account.

  • Agent analyze performance

    "How is my team performing on outbound?" (synthesized narrative report)

  • Agent build lead scores

    "Build an account score for India-based EV / clean-energy companies."

  • Agent connect mailbox

    "Connect my Gmail / Outlook." | "Apply best-practice send settings."

  • Agent draft sequence copy

    "Draft a 6-step multichannel sequence (3 emails, 2 calls, 1 LinkedIn) for healthcare

  • Agent explain howto

    "How do I connect Apollo to Salesforce / reset my password?"

See all 99 Apollo.io 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 Apollo.io 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