Skip to main content
Book a demo

Connect Salesforce to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

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

    Cline CLI setup guide
  3. 3

    Sign in to Salesforce

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

  4. 4

    Use Salesforce from Cline CLI

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

Tools

21 Salesforce tools in Cline CLI

Runlayer policy decides which of these Cline CLI users can call. 7 read data only and 1 can change or delete data.

  • Create record

    Create a new Salesforce record.

  • Delete record

    Delete a Salesforce record by ID.

  • Describe object

    Get detailed metadata for a specific Salesforce sObject including all fields, their types, picklist values, relationships, and constraints.

  • Get limits

    Get the org's API usage limits including daily API calls, data storage, file storage, and other governor limits.

  • Get record

    Retrieve a single Salesforce record by its ID.

  • List objects

    List all sObjects (standard and custom objects) available in the Salesforce org.

  • Query

    Execute a SOQL (Salesforce Object Query Language) query.

  • Query more

    Retrieve the next page of results from a SOQL query.

See all 21 Salesforce 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 Salesforce 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