Connect Ahrefs to Cline CLI
Give Cline CLI governed access to Ahrefs’s 135 tools through Runlayer, with identity, policy, scanning, and audit on every call.
Set up
Add Ahrefs to Cline CLI in four steps
Admins approve the server once. Everyone in Cline 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 Cline CLI to Runlayer
Users add the Runlayer Plugin to Cline CLI by following Runlayer’s setup guide. Cline CLI reaches Ahrefs’s 135 tools through the Runlayer Plugin’s search and execute tools instead of listing each one.
Cline 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 Cline CLI
Ahrefs’s approved tools appear in Cline CLI. Every call is checked against policy and recorded.
Tools
135 Ahrefs tools in Cline CLI
Runlayer policy decides which of these Cline 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 Cline CLI
Some controls apply to every client at the gateway. Others depend on what Cline CLI exposes to Runlayer.
Gateway policy (available)
Every Ahrefs 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