Semrush MCP Server

Created By
mrkooblua year ago
A Model Context Protocol (MCP) server implementation that provides tools for accessing Semrush API data.
Overview

What is Semrush MCP Server?

Semrush MCP Server is a Model Context Protocol (MCP) server implementation that provides tools for accessing Semrush API data, enabling users to analyze domains, keywords, backlinks, and traffic.

How to use Semrush MCP Server?

To use the Semrush MCP Server, clone the repository, install dependencies, set up your Semrush API key in a .env file, build the project, and start the server using npm commands.

Key features of Semrush MCP Server?

  • Domain Analytics: Overview, organic and paid keywords analysis, competitor analysis.
  • Keyword Analytics: Overview data and related keyword discovery.
  • Backlink Analysis: Backlink data and referring domains analysis.
  • Traffic Analytics: Traffic summary and sources analysis (requires .Trends API subscription).

Use cases of Semrush MCP Server?

  1. Analyzing domain performance and SEO metrics.
  2. Discovering new keywords for content strategy.
  3. Evaluating backlink profiles for competitive analysis.
  4. Monitoring traffic sources for marketing insights.

FAQ from Semrush MCP Server?

  • What is required to run the server?

You need a Semrush API key and Node.js installed on your machine.

  • Can I use this server for free?

The server itself is free, but accessing Semrush API data may incur costs based on your API usage.

  • How do I secure my API key?

Never share your API key publicly and store it securely in your environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
mrkooblu
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago