Skip to main content
Book a demo

Connect Ordinal to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

Add Ordinal 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 Ordinal in Runlayer

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

    Cline CLI setup guide
  3. 3

    Sign in to Ordinal

    An admin adds Ordinal credentials to Runlayer once. They never sit in the client’s configuration.

  4. 4

    Use Ordinal from Cline CLI

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

Tools

50 Ordinal tools in Cline CLI

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

  • Get analytics cpm

    Get CPM Values - Retrieve the current CPM (Cost Per Mille) values used for EMV calculations across all platforms.

  • Update analytics cpm

    Update CPM Values - Update the CPM values used for EMV calculations.

  • Analytics linkedin followers

    Retrieve follower count history for a LinkedIn profile.

  • Analytics linkedin posts

    Retrieve post analytics for a LinkedIn profile within a date range.

  • Analytics x followers

    Retrieve follower count history for an X profile.

  • Analytics x posts

    Retrieve post analytics for an X profile within a date range.

  • Create approvals

    Create one or more approval requests for a post.

  • Delete approvals

    Delete an approval request.

See all 50 Ordinal 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 Ordinal 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