Skip to main content
Book a demo

Connect Chronosphere to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

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

    Cline CLI setup guide
  3. 3

    Sign in to Chronosphere

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

  4. 4

    Use Chronosphere from Cline CLI

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

Tools

31 Chronosphere tools in Cline CLI

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

  • Get dashboard

    Get dashboards resource

  • Get drop rule

    Get drop-rules resource

  • Get events metadata

    List properties you can query on events

  • Get log

    Get a full log message by its ID.

  • Get log histogram

    Get histogram of logs from a given query

  • Get mapping rule

    Get mapping-rules resource

  • Get monitor

    Get monitors resource

  • Get notification policy

    Get notification-policies resource

See all 31 Chronosphere 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 Chronosphere 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