Skip to main content
Book a demo

Connect Gem to Cline CLI

Give Cline CLI governed access to Gem’s 15 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo Cline CLI setup guide

Set up

Add Gem to Cline CLI in four steps

Admins approve the server once. Everyone in Cline CLI then gets it through the same governed connection.

  1. 1

    Add Gem to Runlayer

    Gem isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect Cline CLI to Runlayer

    Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Gem’s 15 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to Gem

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

  4. 4

    Use Gem from Cline CLI

    Gem’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.

Tools

15 Gem tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call.

  • Get application

    Look up one application (a candidate on a specific job) by ext_id — status, stage, stage_entry, gem_status (the Talent Pipeline's computed next-step status and SLA health, e.g. NEEDS_DECISION /…

  • Get job

    Look up one job by ext_id — title, status, requisition id, ATS, department/office, and link.

  • Get metrics catalog

    List the metrics and dimensions this team can report on with query_metrics.

  • Get person

    Look up one candidate by ext_id — name, current title, company, school, emails, phone numbers, and links, plus optional fields (full work history, education, custom fields, applications, activity…

  • Get project

    Look up one project by ext_id — name, description, owner, link, type, privacy, archived status, and people_count (candidates in the project).

  • Get saved report

    Look up one saved analytics report (Pipeline Analytics or Outreach) by ext_id — its name, type, owner, link, and a ready-to-run query_metrics payload translated from the report's saved configuration.

  • Get sequence

    Look up one outreach sequence by ext_id — name, status, whether it is a reusable template (is_template) and whether it is archived (is_archived), owner, link, a version (the sequence's edit version —…

  • Get sequence tokens

    List the merge tokens available for writing a sequence stage's subject or body on this team.

See all 15 Gem tools

Control

What Runlayer can see and stop in Cline CLI

Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.

  • Gateway policy (available)

    Every Gem call from Cline CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, Cline 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 before Cline CLI runs it.

  • Block output after it runs (not available)

    Cline CLI ignores Runlayer after a tool runs, so Runlayer cannot block its output. The gateway still applies policy to the call.

  • Redact output in place (not available)

    Runlayer cannot mask tool output in Cline CLI. The gateway still applies policy to the call.

In Cline CLI

  • If Runlayer’s hook times out or crashes, Cline CLI lets the tool call through.
  • This covers the Cline CLI, not the Cline extension for VS Code.

Frequently asked questions

Connect more

Find another combination