Skip to main content
Book a demo

Connect Navattic to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

    Navattic 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 Navattic’s 62 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.

    Cline CLI setup guide
  3. 3

    Sign in to Navattic

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

  4. 4

    Use Navattic from Cline CLI

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

Tools

62 Navattic tools in Cline CLI

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

  • Create brain asset

    Add a URL, FILE, or TEXT asset to an agent's brain.

  • Create launchpad share link

    Create a launchpad share link, sourced from either a set of custom flows or a demo.

  • Delete brain asset

    Permanently delete a Brain asset.

  • Get account

    Get a detailed profile for a specific company account by ID.

  • Get agent demo

    Get a Navattic agent's configuration — objective, personality, tone, FAQs, pronunciations, CTA, welcome screen, language, voice, avatar, escalation/interruption flags, and the linked environment.

  • Get agent demo session

    Get full details for a Navattic agent session: parsed transcript turns, qualifications, summary, sentiment, signals detected, outcome reached, status, end user, and the Steel session viewer URL for…

  • Get agent environment

    Get an agent environment and its folder/flow tree.

  • Get demo

    Get a specific demo.

See all 62 Navattic 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 Navattic 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