2,500+ MCP servers ready to use
Vinkius

Semrush MCP Server for CrewAI 8 tools — connect in under 2 minutes

Built by Vinkius GDPR 8 Tools Framework

Connect your CrewAI agents to Semrush through Vinkius, pass the Edge URL in the `mcps` parameter and every Semrush tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Semrush Specialist",
    goal="Help users interact with Semrush effectively",
    backstory=(
        "You are an expert at leveraging Semrush tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Semrush "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 8 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)
Semrush
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Semrush MCP Server

Equip your conversational workflow with the raw data power of Semrush, the industry standard for Digital Marketing visibility. Through this server, your AI can pull immense amounts of SERP forensics directly into the context window. Stop switching tabs to look up keyword difficulty—just command your agent to fetch it seamlessly.

When paired with CrewAI, Semrush becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Semrush tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

  • Deep Domain Forensics (Competitors) — Query domain_overview or domain_vs_domain to tell your agent to digest the exact organic search volume differences between you and a rival
  • Keyword Strategy Building — Hand a seed topic to the LLM and invoke related_keywords. The AI will compile comprehensive editorial briefs loaded with actual search volumes and CPCs
  • Backlink Auditing — Track the inbound link profile (get_backlinks) of external domains to gauge authority natively within chat sessions
  • Technical SEO Interrogation — Quickly bring your technical site_audit score to the AI, asking it to explain what the flagged errors mean and draft instructions to fix missing metadata

The Semrush MCP Server exposes 8 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Semrush to CrewAI via MCP

Follow these steps to integrate the Semrush MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

03

Customize the agent

Adjust the role, goal, and backstory to fit your use case

04

Run the crew

Run python crew.py. CrewAI auto-discovers 8 tools from Semrush

Why Use CrewAI with the Semrush MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Semrush through the Model Context Protocol.

01

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

02

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

03

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

04

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Semrush + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Semrush MCP Server delivers measurable value.

01

Automated multi-step research: a reconnaissance agent queries Semrush for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

02

Scheduled intelligence reports: set up a crew that periodically queries Semrush, analyzes trends over time, and generates executive briefings in markdown or PDF format

03

Multi-source enrichment pipelines: chain Semrush tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

04

Compliance and audit automation: a compliance agent queries Semrush against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Semrush MCP Tools for CrewAI (8)

These 8 tools become available when you connect Semrush to CrewAI via MCP:

01

domain_overview

Specify the database (e.g., "us", "uk") if targeting a specific region. Get domain SEO overview: rank, organic traffic, paid traffic

02

domain_vs_domain

Compare two domains SEO side by side

03

get_backlinks

Get backlink overview for a domain

04

keyword_overview

Get keyword metrics: volume, CPC, competition, SERP features

05

organic_keywords

Useful for competitor analysis or performance tracking. Get domain organic keyword positions

06

related_keywords

Ideal for content planning and SEO expansion. Get related keywords with volume and difficulty

07

site_audit

Requires a valid Semgrep project ID. Get site audit quality overview for a project

08

traffic_analytics

Get traffic analytics: visits, bounce rate, pages/visit

Example Prompts for Semrush in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Semrush immediately.

01

"Pull the foundational organic ranking and paid traffic overview for the domain 'airbnb.com'. Target the US database."

02

"Find 10 related keywords for the term 'buy mechanical keyboard' including their respective difficulties and search volumes."

03

"Compare the overarching inbound domain performance between 'coca-cola.com' and 'pepsi.com'."

Troubleshooting Semrush MCP Server with CrewAI

Common issues when connecting Semrush to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.
02

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".
03

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.
04

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Semrush + CrewAI FAQ

Common questions about integrating Semrush MCP Server with CrewAI.

01

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.
02

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.
03

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.
04

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.
05

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

Connect Semrush to CrewAI

Get your token, paste the configuration, and start using 8 tools in under 2 minutes. No API key management needed.