Skip to main content
Book a demo

Connect lemlist to GitHub Copilot CLI

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

Book a demo GitHub Copilot CLI setup guide

Set up

Add lemlist 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

    Approve lemlist in Runlayer

    Add lemlist from the catalog and choose who can use it and which of its tools are allowed.

  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 lemlist’s 35 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 lemlist

    Each user signs in to lemlist with OAuth. Runlayer keeps the tokens out of the client’s configuration.

  4. 4

    Use lemlist from GitHub Copilot CLI

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

Tools

35 lemlist tools in GitHub Copilot CLI

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

  • Ask question

    Ask user questions with multiple-choice options.

  • Get team info

    Get basic team info (ID, name, plan, credits remaining).

  • Get team members

    Get all team members with ID, email, name, and role.

  • Get team overview

    Get a quick summary of your account: total campaigns count and breakdown by status (draft, running, paused, ended, archived, errors).

  • Get campaigns

    List campaigns with details (id, name, status, leadsCount).

  • Get campaigns reports

    Get lifetime stats for MULTIPLE campaigns in one call.

  • Get campaign details

    Get configuration and settings for ONE campaign (timezone, emoji, sequences).

  • Get campaign sequences

    Get the email sequences and their content (subject, body) for a specific campaign.

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