How to integrate Semrush MCP with OpenAI Agents SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Semrush Logo
open-ai-agents-sdk Logo
divider

Introduction

This guide walks you through connecting Semrush to the OpenAI Agents SDK using the Composio tool router. By the end, you'll have a working Semrush agent that can show top anchor texts for example.com, compare backlink profiles for three domains, get keyword overview for 'organic coffee', list ad copies seen for my competitor through natural language commands.

This guide will help you understand how to give your OpenAI Agents SDK agent real control over a Semrush account through Composio's Semrush MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your OpenAI and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Semrush
  • Configure an AI agent that can use Semrush as a tool
  • Run a live chat session where you can ask the agent to perform Semrush operations

What is open-ai-agents-sdk?

The OpenAI Agents SDK is a lightweight framework for building AI agents that can use tools and maintain conversation state. It provides a simple interface for creating agents with hosted MCP tool support.

Key features include:

  • Hosted MCP Tools: Connect to external services through hosted MCP endpoints
  • SQLite Sessions: Persist conversation history across interactions
  • Simple API: Clean interface with Agent, Runner, and tool configuration
  • Streaming Support: Real-time response streaming for interactive applications

What is the Semrush MCP server, and what's possible with it?

The Semrush MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Semrush account. It provides structured and secure access to your SEO, keyword, and advertising analytics, so your agent can perform actions like keyword research, competitor analysis, backlink audits, and ad copy retrieval automatically on your behalf.

  • Comprehensive keyword research and reporting: Let your agent fetch broad match keywords, generate batch keyword overviews, and analyze key SEO metrics like search volume and difficulty in real time.
  • Competitor and backlink analysis: Ask your agent to pull backlink profiles, perform batch comparisons of domains, and summarize backlink authority and link types for competitive intelligence.
  • Ad campaign and copy insights: Have the agent retrieve unique Google Ads copies for any domain, helping you benchmark and optimize your own ad strategies based on real competitor data.
  • Content and category profiling: Enable your agent to analyze and categorize domains or URLs, surfacing topic strengths and audience focus areas for smarter content planning.
  • Anchor text and authority monitoring: Direct your agent to report on anchor text distributions and authority score profiles, giving you actionable insights for improving link-building efforts.

Supported Tools & Triggers

Tools
Get ad copiesRetrieves unique ad copies semrush has observed for a specified domain from a regional database, detailing ads seen in google's paid search results.
Get anchor textsUse this action to get a csv report of anchor texts for backlinks pointing to a specified, publicly accessible domain, root domain, or url.
Get authority score profileRetrieves the authority score (as) profile for a specified target, showing the count of referring domains that link to the target for each as value from 0 to 100.
Get backlinksFetches backlinks for a specified domain or url as a csv-formatted string, allowing customization of columns, sorting, and filtering; ensure `display limit` surpasses `display offset` when an offset is used, and note the `urlanchor` filter may have limitations for targets with extensive backlinks.
Backlinks overviewProvides a csv-formatted summary of backlinks, including authority score and link type breakdowns, for a specified and publicly accessible domain, root domain, or url.
Batch comparisonCompares backlink profiles for multiple specified targets (domains, subdomains, or urls) to analyze and compare link-building efforts.
Batch keyword overviewFetches a keyword overview report from a semrush regional database for up to 100 keywords, providing metrics like search volume, cpc, and keyword difficulty.
Broad match keywordFetches broad match keywords for a given phrase; `display sort` and `display filter` parameters are defined but currently not utilized by the api call.
Get categoriesRetrieves categories and their 0-1 confidence ratings for a specified domain, subdomain, or url, with results sorted by rating.
Get categories profileRetrieves a profile of content categories from referring domains for a specified target, analyzing its first 10,000 referring domains and sorting results by domain count.
Get competitor dataRetrieves a customizable csv report of competitors for a specified target (root domain, domain, or url) based on shared backlinks or referring domains, ensuring the target is valid and its type is correctly specified.
Get competitors in organic searchUse to get a domain's organic search competitors from semrush as a semicolon-separated string; `display date` requires 'yyyymm15' format if used.
Get competitors in paid searchRetrieves a list of a domain's competitors in paid search results from a specified regional database.
Get domain ad historyRetrieves a domain's 12-month advertising history from semrush (keywords bid on, ad positions, ad copy) for ppc strategy and competitor analysis; most effective when the domain has ad history in the selected database.
Get domain organic pagesFetches a report on a domain's unique organic pages ranking in google's top 100 search results, with options for specifying database, date, columns, sorting, and filtering.
Get domain organic search keywordsRetrieves organic search keywords for a domain from a specified semrush regional database; `display positions` must be set if `display daily=1` for daily updates.
Get domain organic subdomainsRetrieves a report on subdomains of a given domain that rank in google's top 100 organic search results for a specified regional database.
Get domain paid search keywordsFetches keywords driving paid search traffic to a specified, existing domain using a supported semrush regional database.
Get PLA search keywords for a domainRetrieves product listing ad (pla) search keywords for a specified domain from a semrush regional database.
Compare domainsAnalyzes keyword rankings by comparing up to five domains to find common, unique, or gap keywords, using specified organic/paid types and comparison logic in the `domains` string.
Get historical dataRetrieves monthly historical backlink and referring domain data for a specified root domain, returned as a time series string with newest records first.
Get indexed pagesRetrieves a list of indexed pages from semrush for a specified `target` (root domain, domain, or url) and `target type`, ensuring `target` is publicly accessible, semrush-analyzable, and correctly matches `target type`.
Get keyword difficultyDetermines the keyword difficulty (kd) score (0-100, higher means greater difficulty) for a given phrase in a specific semrush regional database to assess its seo competitiveness.
Keyword overview all databasesFetches a keyword overview from semrush for a specified phrase, including metrics like search volume, cpc, and competition.
Get keyword overview for one databaseFetches a keyword summary for a specified phrase from a chosen regional database.
Get keywords ads historyFetches a historical report (last 12 months) of domains advertising on a specified keyword in google ads, optionally for a specific month ('yyyymm15') or the most recent period, returning raw csv-like data.
Get organic resultsRetrieves up to 100,000 domains and urls from google's top 100 organic search results for a keyword and region, returning a raw string; use `display date` in 'yyyymm15' format (day must be '15') for historical data.
Get paid search resultsFetches domains ranking in google's paid search results (adwords) for a specified keyword and regional database.
Phrase questionsFetches question-format keywords semantically related to a given query phrase for a specified regional database, aiding in understanding user search intent and discovering content ideas.
Get PLA competitorsRetrieves domains competing with a specified domain in google's product listing ads (pla) from a given semrush regional database.
Get PLA copiesFetches product listing ad (pla) copies that semrush observed for a domain in google's paid search results.
Get referring domainsRetrieves a report as a text string (e.
Get referring domains by countryGenerates a csv report detailing the geographic distribution of referring domains (by country, determined via ip address) for a specified, publicly accessible target.
Referring i psFetches ip addresses that are sources of backlinks for a specified target domain, root domain, or url.
Find related keywordsCall this to find related keywords (including synonyms and variations) for a target phrase in a specific regional database; `display date` (if used for historical data) must be 'yyyymm15' for a past month.
Get TLD distributionFetches a report on the top-level domain (tld) distribution of referring domains for a specified target, useful for analyzing geographic or categorical backlink diversity.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and OpenAI API Key
  • Primary know-how of OpenAI Agents SDK
  • A live Semrush project
  • Some knowledge of Python or Typescript

Getting API Keys for OpenAI and Composio

OpenAI API Key
  • Go to the OpenAI dashboard and create an API key. You'll need credits to use the models, or you can connect to another model provider.
  • Keep the API key safe.
Composio API Key

Install dependencies

pip install composio_openai_agents openai-agents python-dotenv

Install the Composio SDK and the OpenAI Agents SDK.

Set up environment variables

bash
OPENAI_API_KEY=sk-...your-api-key
COMPOSIO_API_KEY=your-api-key
USER_ID=composio_user@gmail.com

Create a .env file and add your OpenAI and Composio API keys.

Import dependencies

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession
What's happening:
  • You're importing all necessary libraries.
  • The Composio and OpenAIAgentsProvider classes are imported to connect your OpenAI agent to Composio tools like Semrush.

Set up the Composio instance

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())
What's happening:
  • load_dotenv() loads your .env file so OPENAI_API_KEY and COMPOSIO_API_KEY are available as environment variables.
  • Creating a Composio instance using the API Key and OpenAIAgentsProvider class.

Create a Tool Router session

# Create a Semrush Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["semrush"]
)

mcp_url = session.mcp.url

What is happening:

  • You give the Tool Router the user id and the toolkits you want available. Here, it is only semrush.
  • The router checks the user's Semrush connection and prepares the MCP endpoint.
  • The returned session.mcp.url is the MCP URL that your agent will use to access Semrush.
  • This approach keeps things lightweight and lets the agent request Semrush tools only when needed during the conversation.

Configure the agent

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Semrush. "
        "Help users perform Semrush operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)
What's happening:
  • We're creating an Agent instance with a name, model (gpt-5), and clear instructions about its purpose.
  • The agent's instructions tell it that it can access Semrush and help with queries, inserts, updates, authentication, and fetching database information.
  • The tools array includes a HostedMCPTool that connects to the MCP server URL we created earlier.
  • The headers dict includes the Composio API key for secure authentication with the MCP server.
  • require_approval: 'never' means the agent can execute Semrush operations without asking for permission each time, making interactions smoother.

Start chat loop and handle conversation

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())
What's happening:
  • The program prints a session URL that you visit to authorize Semrush.
  • After authorization, the chat begins.
  • Each message you type is processed by the agent using Runner.run().
  • The responses are printed to the console, and conversations are saved locally using SQLite.
  • Typing exit, quit, or q cleanly ends the chat.

Complete Code

Here's the complete code to get you started with Semrush and open-ai-agents-sdk:

import asyncio
import os
from dotenv import load_dotenv

from composio import Composio
from composio_openai_agents import OpenAIAgentsProvider
from agents import Agent, Runner, HostedMCPTool, SQLiteSession

load_dotenv()

api_key = os.getenv("COMPOSIO_API_KEY")
user_id = os.getenv("USER_ID")

if not api_key:
    raise RuntimeError("COMPOSIO_API_KEY is not set. Create a .env file with COMPOSIO_API_KEY=your_key")

# Initialize Composio
composio = Composio(api_key=api_key, provider=OpenAIAgentsProvider())

# Create Tool Router session
session = composio.create(
    user_id=user_id,
    toolkits=["semrush"]
)
mcp_url = session.mcp.url

# Configure agent with MCP tool
agent = Agent(
    name="Assistant",
    model="gpt-5",
    instructions=(
        "You are a helpful assistant that can access Semrush. "
        "Help users perform Semrush operations through natural language."
    ),
    tools=[
        HostedMCPTool(
            tool_config={
                "type": "mcp",
                "server_label": "tool_router",
                "server_url": mcp_url,
                "headers": {"x-api-key": api_key},
                "require_approval": "never",
            }
        )
    ],
)

print("\nComposio Tool Router session created.")

chat_session = SQLiteSession("conversation_openai_toolrouter")

print("\nChat started. Type your requests below.")
print("Commands: 'exit', 'quit', or 'q' to end\n")

async def main():
    try:
        result = await Runner.run(
            agent,
            "What can you help me with?",
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")
    except Exception as e:
        print(f"Error: {e}\n")

    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit", "q"}:
            print("Goodbye!")
            break

        result = await Runner.run(
            agent,
            user_input,
            session=chat_session
        )
        print(f"Assistant: {result.final_output}\n")

asyncio.run(main())

Conclusion

This was a starter code for integrating Semrush MCP with OpenAI Agents SDK to build a functional AI agent that can interact with Semrush.

Key features:

  • Hosted MCP tool integration through Composio's Tool Router
  • SQLite session persistence for conversation history
  • Simple async chat loop for interactive testing
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Semrush MCP Agent with another framework

Claude Agent SDK

Claude Agent SDK

Use Semrush MCP with Claude Agent SDK

Google ADK

Google ADK

Use Semrush MCP with Google ADK

LangChain

LangChain

Use Semrush MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Semrush MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Semrush MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Semrush MCP with LlamaIndex

CrewAI

CrewAI

Use Semrush MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Semrush MCP?

With a standalone Semrush MCP server, the agents and LLMs can only access a fixed set of Semrush tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Semrush and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with OpenAI Agents SDK?

Yes, you can. OpenAI Agents SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Semrush tools.

Can I manage the permissions and scopes for Semrush while using Tool Router?

Yes, absolutely. You can configure which Semrush scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Semrush data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free