Semrush Domain Metrics MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | Yes | Your Apify API token, from console.apify.com/account/integrations. The server lists its tool without a token; a call needs one. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_semrush_domain_metricsA | Look up domains on Semrush's public website pages. Returns one row per domain with Authority Score, visits, organic and paid traffic, backlinks, rank, competitors, and keywords. Reads run 20 seconds apart. Semrush has a public page for some domains only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With a single tool there is no possibility of confusion; an agent can only call get_semrush_domain_metrics, and its purpose is clearly stated.
The lone name follows a clear provider_resource pattern in snake_case (get_semrush_domain_metrics), so there are no mixed conventions to reconcile.
One tool is thin for a server that bundles several distinct data domains (traffic, backlinks, ranks, keywords, competitors) into a single all-or-nothing lookup.
The lookup returns a broad set of metrics per domain, but there is no way to request specific metrics, handle multiple domains efficiently (reads 20s apart), or access non-public domains — leaving notable gaps and dead ends.