Connect Semrush to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Semrush’s 23 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Semrush to GitHub Copilot CLI in four steps
Admins approve the server once. Everyone in GitHub Copilot CLI then gets it through the same governed connection.
- 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
Connect GitHub Copilot CLI to Runlayer
Users add the Runlayer Plugin to GitHub Copilot CLI by following Runlayer’s setup guide. GitHub Copilot CLI reaches Semrush’s 23 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 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
Use Semrush from GitHub Copilot CLI
Semrush’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
23 Semrush tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot 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…
Control
What Runlayer can see and stop in GitHub Copilot CLI
Some controls apply to every client at the gateway. Others depend on what GitHub Copilot CLI exposes to Runlayer.
Gateway policy (available)
Every Semrush call from GitHub Copilot CLI passes through Runlayer, where your policies can allow, alert, mask, or block it.
Audit trail (available)
Each call is recorded with the user, GitHub Copilot 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 or permission request before GitHub Copilot CLI runs it.
Block output after it runs (available)
Runlayer can block a tool’s output before GitHub Copilot CLI’s model sees it.
Redact output in place (available)
Runlayer can mask sensitive parts of a successful tool’s output in GitHub Copilot CLI and pass the rest through.
In GitHub Copilot CLI
- When a tool fails, Runlayer records the error but cannot replace it.
Frequently asked questions
Connect more