Connect Claude, ChatGPT, Cursor (or any AI assistant that supports MCP) and it can run localized searches, track your rankings and pull reports for you. No more copy-pasting between tabs: paste one link, approve access in your browser, done.
Clauderun_proxy_search isearchfrom · mcp{ "q": "running shoes", "country": "DE", "city": "Berlin", "device": "mobile" } A few of the workflows an MCP-connected agent handles end to end.
3 keywords up, 1 slipped · full brief in #seo
| running shoes | #4 | 2 |
| trail runners | #7 | 3 |
| marathon gear | #11 | 1 |
| racing flats | #9 | 2 |
A scheduled agent pulls the week's position checks, writes the summary and posts it before you're at your desk.
The agent runs the ad tracker, compares the results and pings you the moment a new competitor bids on your keywords.
Berlin #4
London #7
New York #12Ask Cursor or Claude Code how a page ranks in three markets mid-review. The answer lands in the same chat.
ChatGPT #2 Mentioned
Gemini #4 Mentioned
Perplexity Missingsemrush.comOne prompt sweeps ChatGPT, Gemini and Perplexity for your brand: mentions, sentiment and who's recommended instead.
Six clients pictured, hundreds supported. Anything that speaks MCP plugs into the same URL.
Claude Claude Code ChatGPT…and any other MCP client
Seven tool families cover the whole workflow (searches, campaigns, projects and usage), plus a way to ask questions across all your data.
Run Google or Bing searches from any country, city, language and device: full scraped result pages or direct search URLs.
run_proxy_searchrun_direct_searchget_search_optionsAsk in plain language ("which keywords dropped this month?") and your agent turns it into a safe, read-only query across your rankings, ads, mentions and searches. It can read everything in your workspace and change nothing.
SELECT keyword, MIN(position) AS best FROM serp_position_results WHERE checked_at > now() - '7 days' GROUP BY keyword ORDER BY best ASC;
query_sqldescribe_schemaCreate campaigns, trigger runs and read keyword rankings by location.
create_position_campaigntrigger_position_runWatch competitors' paid placements: campaigns, runs and per-keyword ad captures.
create_ad_tracker_campaigntrigger_ad_tracker_runTrack brand mentions across ChatGPT, Gemini and Perplexity answers, on schedule or on demand.
create_ai_visibility_campaigntrigger_ai_visibility_runList, create and organize projects so agents keep work tidy across clients.
list_projectscreate_projectBalance, plan limits and the full usage history, so agents can budget their own token spend.
whoamiget_token_balanceget_token_transactionsNothing to install, no code to write, no API keys to juggle. Point your AI app at one link, approve access in your browser, and the tools show up on their own.
Claude, ChatGPT, Cursor and every other MCP client accept a remote server URL. Paste ours once. There's nothing to install and nothing to keep running.
https://api.isearchfrom.com/mcp Your browser opens a consent screen. Pick the workspace and tick only what you're delegating: read searches, run searches, manage campaigns. What you approve is all the agent ever gets, and you can revoke it anytime.
Your agent discovers all 32 tools on its own. There's nothing to configure. Ask a question in plain language and it picks the right tool, whether that's a one-off search from Berlin or a dig through your whole ranking history.
run_proxy_searchquery_sqltrigger_position_runcreate_ai_visibility_campaignget_token_balancetrigger_ad_tracker_runlist_projectswhoami +24 moreEvery tool call clears four gates before it touches a row of data. Agents get exactly the reach you granted, nothing more, and never another workspace's data.
Model Context Protocol is the open standard AI assistants use to call external tools. Connecting iSearchFrom over MCP means Claude, Cursor, ChatGPT and other agents can run searches, manage campaigns and query results for you, instead of you copy-pasting between tabs.
Any MCP client that supports remote servers: Claude (web, desktop and Claude Code), Cursor, Windsurf, ChatGPT (with developer mode enabled), VS Code and more. If your tool speaks MCP, it can connect.
The MCP server is included in the Team plan. It's separate from API access, and unlike the API there's nothing to code: you connect straight from your AI app's settings.
There's no separate metering. Tool calls spend the same token balance as the app: a proxy search costs one token per page, tracker runs one token per keyword or check. All reads (results, analytics, SQL) are free.
Only if you let it. Write and delete capabilities are individual checkboxes on the consent screen. Grant read-only access and the agent can look but never touch.
Every connection is bound to one workspace. Row-level security pins queries to that workspace at the database layer, the SQL tool runs on a read-only role with column-level grants, and system tables are unreachable.
Revoke the connection at any time. The token dies immediately. Role downgrades propagate too, since permissions are re-checked live on every call.
Connect your assistant in under a minute and hand off the busywork (localized checks, tracking runs, reports) while you keep full control of what it can touch.
https://api.isearchfrom.com/mcp