Skip to main content
Book a demo

Connect Monday to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

    Approve Monday in Runlayer

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

  2. 2

    Connect Cline CLI to Runlayer

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

    Cline CLI setup guide
  3. 3

    Sign in to Monday

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

  4. 4

    Use Monday from Cline CLI

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

Tools

101 Monday tools in Cline CLI

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

  • Agent catalog

    Browse the account-wide catalog of available trigger types and skills for monday platform agents.

  • Read all API

    Execute read-only GraphQL queries against the monday.com API.

  • Write all API

    Execute GraphQL mutations against the monday.com API to create, update, or delete data.

  • All Monday API

    Execute any monday.com API operation by generating GraphQL queries and mutations dynamically.

  • All widgets schema

    Fetch complete JSON Schema 7 definitions for all available widget types in monday.com.

  • Board insights

    Allows you to calculate insights about board's data by filtering, grouping and aggregating columns.

  • Change item column values

    Change the column values of a single item on a monday.com board.

  • Connect external agent

    Connect a custom external agent (an agent running on your own server/infra) to monday.com.

See all 101 Monday 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 Monday 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