Connect Ahrefs to GitHub Copilot CLI
Give GitHub Copilot CLI governed access to Ahrefs’s 135 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ahrefs 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
Approve Ahrefs in Runlayer
Add Ahrefs from the catalog and choose who can use it and which of its tools are allowed.
- 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 Ahrefs’s 135 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
GitHub Copilot CLI setup guide - 3
Sign in to Ahrefs
Sign in the way Ahrefs requires. Runlayer holds the credentials so they stay out of the client’s configuration.
- 4
Use Ahrefs from GitHub Copilot CLI
Ahrefs’s approved tools appear in GitHub Copilot CLI. Every call is checked against policy and recorded.
Tools
135 Ahrefs tools in GitHub Copilot CLI
Runlayer policy decides which of these GitHub Copilot CLI users can call. 93 read data only.
Batch analysis
Performs a batch analysis of multiple URLs, domains, or subdomains to retrieve selected SEO, backlink, organic, and paid traffic metrics.
Brand radar AI responses
Provides questions asked to AI assistants and the corresponding AI-generated responses that mention your brand or competitors’ brands, including cited sources and search volume estimates.
Brand radar AI responses entities
Provides questions asked to AI assistants and the corresponding AI-generated responses that mention your brand or competitors’ brands, including cited sources and search volume estimates.
Brand radar citations history entities
Provides the historical number of citations for your and competitors' brand URLs in an LLM you specify.
Brand radar citations overview entities
Provides the number of citations for your and competitors's brands in an LLM you specify, with filters for locations, query text, URL, and more.
Brand radar cited domains
Provides domains cited in AI-generated responses that mention your brand or competitors' brands in an LLM you specify, including how many responses referenced each domain (broken down by brand) and…
Brand radar cited domains entities
Provides domains cited in AI-generated responses that mention your brand or competitors' brands in an LLM you specify, including how many responses referenced each domain (broken down by brand) and…
Brand radar cited pages
Provides the pages cited in AI-generated responses that mention your brand or competitors' brands in an LLM you specify, including how many responses referenced each page (broken down by brand) and…
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 Ahrefs 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