Skip to main content
Book a demo

Connect Semrush to Cline CLI

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

Book a demo Cline CLI setup guide

Set up

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

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

    Cline CLI setup guide
  3. 3

    Sign in to Semrush

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

  4. 4

    Use Semrush from Cline CLI

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

Tools

23 Semrush tools in Cline CLI

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

  • Audience research

    Audience Analytics: visitor profile of a domain — demographics (age, gender, income, education, household size, occupation), audience interests, visitor geography by country, audience overlap between…

  • Backlink research

    Backlink profile analysis: referring domains, anchor texts, authority scores, link growth history, and competitor link comparison.

  • Backlinks research

    Backlink Analytics: for a single domain's link profile — backlinks, referring domains and IPs, anchor texts, geographic and TLD distribution, Authority Score breakdown, domain and referring-domain…

  • Competitors research

    Competitive Research: find who competes with a domain in organic search, paid search, and Google Shopping (PLA); compare keyword overlap and backlink profiles between multiple domains; analyze market…

  • Domain overview

    Get high-level counters for a domain, subdomain, subfolder, or URL — Semrush Rank, keyword/traffic/cost totals, PLA, SERP Features.

  • Execute report

    Execute any Semrush report.

  • Get report schema

    Get a report's parameters.

  • Keyword research

    Keyword Analytics: look up any keyword — search volume, CPC, competition, keyword difficulty, SERP results (organic and paid), related keywords, broad match variations, phrase questions, and ads…

See all 23 Semrush 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 Semrush 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