How is this different from connecting Semrush MCP directly?

Connected directly, an agent sees every tool the server exposes and holds the credential itself. Through TrustGate you choose which tools each agent gets, and every call is logged against the agent that made it.

What if the Semrush MCP API changes?

We track the Semrush MCP schema, so the tool catalogue stays current. Tools you have already allowed keep working, and anything new stays denied until you enable it.

Can I give different agents different Semrush tools?

Yes. Access is set per agent: one can get a handful of read tools, another the full set. You grant the whole MCP or single tools within it.

Where can I see what my agents did in Semrush?

Every call is logged against the agent that made it, with the tool it used. Activity can be sent on to your own monitoring.

Do I need to run the Semrush MCP server myself?

No. TrustGate connects to the Semrush MCP server and sits in front of it. Your agent only talks to your TrustGate URL, never to Semrush directly.

Connect Semrush MCP to your AI agents, securely.

Q: Is Semrush MCP secure?

The server itself exposes 14 tools, and some of them can write to your Semrush account. Behind TrustGate an agent only sees the tools you allow, requests and responses are inspected, and every call is logged. Anything outside the allowlist is denied before it reaches Semrush.

One secured endpoint for every Semrush call your AI agents make, scoped per user, inspected, and logged.

Get started for free

Get a demo

Try Semrush MCP now

What your agents can ask once Semrush MCP is connected.

Select the tools your AI agents can call

14 tools from the Semrush MCP schema.

Showing 14 tools

domain_overviewreadDiscovery tool for domain overview reports across one or all databases, including history, winners and losers, and Semrush Rank.
organic_researchreadDiscovery tool for organic search reports: organic keywords, organic pages and organic subdomains for domains, subdomains, subfolders and URLs.
keyword_researchreadDiscovery tool for keyword reports: keyword overview, batch overview, organic and paid results, related keywords, broad match, phrase questions and keyword difficulty.
competitors_researchreadDiscovery tool for competitor reports in organic and paid search, including domain versus domain comparisons.
backlinks_researchreadDiscovery tool for backlink reports: backlinks, referring domains and IPs, TLD distribution, anchors, indexed pages, competitors, batch comparison, Authority Score and categories.
audience_researchreadDiscovery tool for audience reports: audience insights and interests, age and sex, household, income, education and occupation distribution, and social media.
traffic_overviewreadDiscovery tool for Trends traffic reports: traffic summary, daily and weekly traffic, sources and destinations, geo distribution, subdomains, subfolders, top pages and traffic rank.
paid_search_researchreadDiscovery tool for paid search reports: paid keywords, ads copies and domain ad history.
shopping_researchreadDiscovery tool for product listing ads reports: PLA search keywords, PLA copies and PLA competitors.
position_trackingreadDiscovery tool for position tracking reports: organic and Adwords overview, positions, competitors discovery, visibility index and landing pages. Read-only methods only.
site_auditreadDiscovery tool for site audit reports: campaign and snapshot information, issue descriptions and detail, page information and snapshot history. Read-only methods only.
projectsreadDiscovery tool for the read-only Projects API methods: listing projects and getting information about one. Creating, updating and deleting projects are not exposed.
get_report_schemareadGets the parameters a specific report accepts, to be called between discovery and execution.
execute_reporthigh riskRuns a report. Covers every report in the Trends API, the SEO API and the read-only Projects API methods. Each call consumes API units from the same balance as a direct API request, with the number depending on the report type and the amount of data requested.

What Semrush MCP exposes

Semrush MCP groups its 14 tools into 3 categories, each with a suggested starting policy.

All 14 tools as JSON, ready to paste.

Category	Covers	Access	Suggested policy
Discovery	Finding the available reports across domain overview, organic research, keyword research, competitors, backlinks, audience, traffic overview, paid search, shopping, position tracking, site audit and projects	Read	Read-only and cheap; these only locate the report an agent should run
Execution	Running a report once its parameters are known	Read	One tool name stands for every report in the Trends, SEO and read-only Projects APIs, so the tool name says nothing about which data is pulled or how many units it costs. Cap the call rate and watch the unit balance
Schema	Getting the parameters a specific report accepts	Read	Read-only; the required step between discovery and execution

Connect Semrush MCP to your AI agent

Four steps, under ten minutes.

01
Sign in to NeuralTrust
Open the NeuralTrust platform, sign in and go to Getting started, then Connect your tools.
02
Choose your agent
When asked which agent you use, pick Claude Code, Codex, Cursor, Windsurf, Copilot or your own code.
03
Connect Semrush
Find Semrush in the tool list and connect it.
04
Connect your agent
Follow the steps on screen to add the config to your agent, then send the test prompt.

Permissions down to the single tool

You do not allow Semrush MCP or block it. You allow the exact tools each agent can call, one by one.

Semrush MCP	14 TOOLS AVAILABLE
Code review agent	4 tools, read only
Issue triage bot	9 tools
Platform team assistant	all 14 tools

Tool by toolConnecting the server is not the unit of access. Each tool is granted on its own.
Default denyA tool you have not enabled is never exposed to the agent.
Approval on writesTools that change or delete things can require a human to confirm.

Is Semrush MCP secure?

One endpoint instead of raw credentials. Every call is checked against policy and logged.

AI agentsConnect through your MCP client configuration.	NeuralTrustApply controls based on your configuration.	Semrush MCP14 documented tools. Which reports actually return data depends on the Semrush subscription and the remaining API unit balance.
Coding assistants	Connection & credentialsper user	Discovery12 tools
Internal copilots	Tool access policiesdeny by default	Execution1 tool
Workflow automations	Request & response inspectioninline	Schema1 tool
Compatible MCP clients	Activity monitoringalerts and logs