How to integrate Semrush MCP with Kimi Code

Trusted by
AWS
Glean
Zoom
Airtable

30 min · no commitment · see it on your stack

Semrush logo
Kimi Code logo
divider

How to integrate Semrush MCP with Kimi Code

Kimi Code is Moonshot AI's open-source coding agent, powered by Kimi K2.6. It runs in your terminal, reads and edits code, executes shell commands, and plans multi-step tasks, with native MCP support for extending it to outside tools.

In this guide, I will explain the easiest and most secure way to connect your Semrush account to Kimi Code via Composio Connect, so it can show top anchor texts for example.com, compare backlink profiles for three domains, get keyword overview for 'organic coffee', and more without ever putting your account credentials at risk.

Also integrate Semrush with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Managed OAuth. You do not have to worry about authentication and authorization flows for every app.
  • Programmatic tool calling. Allows LLMs to write code in a remote workbench to handle complex tool chaining. This reduces back-and-forth for frequent tool calls.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Connect Semrush to Kimi Code

Kimi Code is a TypeScript agent distributed through npm. It acts as an MCP client and reads server definitions from an mcp.json file, and it can also add and authenticate servers conversationally through /mcp-config. Composio is a remote HTTP server that authenticates with OAuth, so no API key is stored anywhere.

1. Install Kimi Code

The quickest way is the official install script, which requires no pre-installed Node.js and places the kimi executable on your PATH.

bash
# macOS or Linux
curl -fsSL https://code.kimi.com/kimi-code/install.sh | bash

# Windows PowerShell
irm https://code.kimi.com/kimi-code/install.ps1 | iex

# Confirm the installation
kimi --version

2. Log in

Start Kimi Code in your project directory, then sign in from the interactive UI:

bash
kimi

Run /login and choose Kimi Code OAuth using the device-code flow, or use a Moonshot API key.

3. Add Composio with /mcp-config

In current versions of Kimi Code, MCP servers are managed inside the app, not with a shell subcommand. From the interactive UI, run:

bash
/mcp-config
Kimi Code MCP config flow for adding the Composio MCP server

Tell it the server name and URL in plain language. For example:

Server name is Composio, and here is the server URL: https://connect.composio.dev/mcp

Kimi Code asks whether to add it globally, at ~/.kimi-code/mcp.json, or project-local for the current checkout, then writes the entry for you:

bash
{
  "mcpServers": {
    "Composio": {
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

There is no transport field to set. Kimi Code infers HTTP from the url.

4. Restart the session

The new server is picked up on a fresh session, not the current one. Start a new session:

bash
/new

On the new session, Kimi Code detects that the server needs authorization and prompts you to run:

bash
/mcp-config login Composio

5. Authorize with OAuth

Run the command Kimi suggests:

bash
/mcp-config login composio

Kimi Code opens Composio's authorization page or surfaces a URL. Approve access, then return to the session. You should see confirmation that the Composio MCP server is connected.

Composio authorization page for Kimi Code MCP setup

Check the connection status any time with /mcp. Composio should appear as connected with its tools listed.

Kimi Code showing Composio connected after OAuth authorization

Connect your Semrush account

Back in a Kimi Code session, ask the agent to connect to Semrush or give it any Semrush-related task.

For example, ask it to:

  • "Show top anchor texts for example.com"
  • "Compare backlink profiles for three domains"
  • "Get keyword overview for 'organic coffee'"

It will prompt you to authenticate and authorize access to Semrush.

That is it. Composio tools are now available in Kimi Code, and your Semrush account is ready to use.

Supported Tools & Triggers

Tools
Check Semrush account units balanceTool to fetch the remaining Semrush Standard API units for the authenticated account.
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 semicolon-delimited CSV string (parse with `sep=';'`); allows customization of columns, sorting, and filtering.
Backlinks overviewProvides a semicolon-delimited (sep=';') CSV 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.
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 CSV-formatted report of competitors for a specified target (root domain, domain, or URL) based on shared backlinks or referring domains.
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 semicolon-delimited text report listing domains that link to a target, with options to filter by type (not value).
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.

Conclusion

You have successfully connected Semrush to Kimi Code using Composio Connect. Your agent can now manage Semrush from the terminal with natural language, without exposing credentials in prompts or local scripts.

Since the same Composio endpoint exposes 1,000+ apps, you can add Slack, Calendar, Linear, and more to the same server and chain them into cross-app workflows.

How to build Semrush MCP Agent with another framework

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 Kimi Code?

Yes, you can. Kimi Code 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.