Skip to main content
Glama
Semrush Domain Metrics MCP Server

Semrush Domain Metrics MCP Server

README.md
# Semrush Domain Metrics MCP Server

[![npm version](https://img.shields.io/npm/v/@mambalabsdev/mcp-semrush-domain-metrics)](https://www.npmjs.com/package/@mambalabsdev/mcp-semrush-domain-metrics) [![license](https://img.shields.io/github/license/mambalabsdev/mcp-semrush-domain-metrics)](https://github.com/mambalabsdev/mcp-semrush-domain-metrics/blob/main/LICENSE)

An MCP server for the Mamba Labs Semrush Domain Metrics actor on Apify. Semrush public domain metrics as rows.

## What's Inside

- [What it does](#what-it-does)
- [Quick start](#quick-start)
- [Prerequisites](#prerequisites)
- [Example prompts](#example-prompts)
- [Tool](#tool)
- [Inputs](#inputs)
- [Pricing](#pricing)
- [Full actor documentation](#full-actor-documentation)
- [License](#license)

## What it does

Takes domains and returns one row each with Authority Score, visits, organic and paid traffic, backlinks, rank, competitors, and keywords, from Semrush's public website pages.

All of the work runs on Apify. This package is a thin client that starts the actor run, waits for it, and hands back the dataset rows.

## Quick start

You need Node.js 18 or newer and an Apify account with an API token.

Add this to your Claude Desktop config (`claude_desktop_config.json`), Cursor, or any MCP client:

```json
{
  "mcpServers": {
    "mamba-semrush-domain-metrics": {
      "command": "npx",
      "args": [
        "-y",
        "@mambalabsdev/mcp-semrush-domain-metrics"
      ],
      "env": {
        "APIFY_TOKEN": "your-apify-token"
      }
    }
  }
}
```

Restart the client. The `get_semrush_domain_metrics` tool appears.

## Prerequisites

- Node.js 18 or newer.
- An Apify API token from [console.apify.com/account/integrations](https://console.apify.com/account/integrations), set as `APIFY_TOKEN`. The server lists its tool without a token; a call needs one.

## Example prompts

- "Get the Semrush Authority Score and monthly visits for stripe.com."
- "Compare backlinks and organic traffic for hubspot.com and notion.so."

## Tool

`get_semrush_domain_metrics`. One tool. Example arguments:

```json
{
  "domains": [
    "stripe.com"
  ],
  "max_domains": 1
}
```

## Inputs

Every buyer facing input of the actor. Omitted inputs take the actor's own defaults.

| Input | Type | Required | Description |
|---|---|---|---|
| `domains` | array | no | Domains or URLs to look up, such as stripe.com. Semrush publishes a page for some domains only: in a test of 30, 15 had one. |
| `max_domains` | number | no | Text number from 1 to 1000. Default 100. Reads run 20 seconds apart, so 100 domains take about 33 minutes. Set the run timeout to fit. |
| `max_charge_usd` | number | no | Optional. The run stops before a charge that would pass this amount. Summary rows are always returned. |

## Pricing

Pay per event on Apify, billed to your Apify account. Prices in USD.

| Event | Free plan | Bronze | Silver | Gold |
|---|---|---|---|---|
| `domain-row`, one domain with metrics | $0.01 | $0.0095 | $0.009 | $0.0085 |
| `no-page-row`, one domain with no Semrush page | $0.003 | $0.00285 | $0.0027 | $0.00255 |
| `apify-actor-start`, per run start | $0.002 | $0.002 | $0.002 | $0.002 |

Summaries, refused reads, and refused input are free. Mamba Labs pays the platform costs of the run, Apify proxy traffic included.

## Full actor documentation

[apify.com/mambalabs/semrush-domain-metrics](https://apify.com/mambalabs/semrush-domain-metrics)

## License

MIT. See [LICENSE](LICENSE).

TDQS

A3.9/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

The lone name follows a clear provider_resource pattern in snake_case (get_semrush_domain_metrics), so there are no mixed conventions to reconcile.

Tool Count3/5

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.

Completeness3/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues