Any MCP client · The URL, or mcp-remote
Connect Search Console to any MCP client
RankEcho's MCP server is at https://rankecho.io/mcp, over streamable HTTP with OAuth. A client that supports remote servers connects to it directly; any client that runs a local command can use npx -y mcp-remote https://rankecho.io/mcp. Either way you sign in and pick the sites it may read.
https://rankecho.io/mcpWhat you need
- An MCP client that supports remote servers with OAuth, or one that can run a local command
- RankEcho Search Intelligence: the trial or any paid plan
- Google Search Console connected to RankEcho for at least one site
No RankEcho account yet? Connect Search Console first: the trial includes the connector.
Set it up in Any MCP client
Use the URL
If your client takes a remote server URL, enter it. RankEcho speaks streamable HTTP and signs clients in with OAuth 2.1, dynamic client registration and PKCE.
https://rankecho.io/mcpOr run the bridge
If your client only runs local commands, give it this command. mcp-remote handles the sign-in and passes requests on.
npx -y mcp-remote https://rankecho.io/mcpSign in and choose sites
A RankEcho page opens. Sign in, tick the sites this connection may read, and approve. It gets read-only access to those sites and nothing else.
Ask about your data
Ask in plain words; the client calls RankEcho's tools when it needs data. Start with: Which of my sites can you read, and up to which day?
Check it worked: Your client should list nineteen tools, starting with list_sites. Call it first.
Questions to start with
- Which of my sites can you read, and up to which day?
- Which pages lost the most clicks in the last 28 days compared with the 28 before?
- List my top 5 opportunities and what each would take.
- Which searches show my site on page 2, and which page ranks for each?
- Did the changes I marked done last month help?
What it reads for rankecho.io
We connect RankEcho to our own site. These are the numbers the tools read for rankecho.io, so you can see the size of answer to expect in Any MCP client: the last 28 synced days, 9 October to 5 November 2026, and the 90 days of search rows behind the page and search tools.
Source: rankecho.io's Search Console as RankEcho synced it, read 16 November 2026. Search rows cover 8 August to 5 November 2026.
What Any MCP client can read
Every tool reads; none writes. Each answer comes from RankEcho's synced Search Console data and its Opportunities, for the sites you ticked.
| Tool | What it reads |
|---|---|
list_sites | Which of your sites this connection may read, and whether their data has synced. |
get_data_status | The first and last synced day, and the last 28 days at a glance. |
get_site_overview | Clicks, impressions, CTR and position for any range, with the period before. |
query_performance | Top pages or searches, filtered and sorted, with their change. |
compare_periods | Two ranges side by side, and the pages or searches that moved most. |
list_actions | Quick wins, low CTR pages, decaying pages and content gaps, by clicks at stake. |
get_page_evidence | One page's numbers, its top searches and the actions about it. |
get_action_results | Clicks 28 days before and after each change you marked done. |
list_opportunities | Google, answer box and AI answer opportunities, ranked as in RankEcho. |
list_results | Each test's baseline and its result against control pages and prompts. |
find_striking_distance | Searches just below the top, by the clicks they would gain at a target position. |
check_ctr_benchmark | Your CTR by position against a published curve, and the pages missing clicks. |
find_competing_pages | Searches your own pages split, which page should own each, and the fix. |
find_content_decay | Pages or searches well below their best month, by clicks lost. |
list_new_lost_rankings | Searches you started or stopped ranking for, window against window. |
list_ai_searches | Searches phrased like AI prompts, and whether AI answers cite you for them. |
forecast_traffic | Clicks month by month with seasons, a likely range and a scenario. |
list_experiments | Changes tried on half a group of pages, read against the other half. |
get_index_status | Tracked pages as Google last reported them, and an index health score. |
Questions and fixes
How do I connect Search Console to Any MCP client?
RankEcho's MCP server is at https://rankecho.io/mcp, over streamable HTTP with OAuth. A client that supports remote servers connects to it directly; any client that runs a local command can use npx -y mcp-remote https://rankecho.io/mcp. Either way you sign in and pick the sites it may read.
Can Any MCP client change my site or Search Console through RankEcho?
No. The connection is read-only. It reads the sites you ticked and cannot edit your website, start a sync or change any setting. Disconnect it any time in RankEcho under ChatGPT and AI connections.
Do I need to give it my Google password?
No. You sign in to RankEcho, which already holds your Search Console connection, and pick the sites the assistant may read. Google credentials never reach the assistant.
Which redirect URIs does RankEcho accept?
ChatGPT's and Claude's hosted callbacks, and loopback callbacks on localhost or 127.0.0.1, any port from 1024 to 65535, at /callback or /oauth/callback. Other redirects are refused.
The browser never opens
mcp-remote opens the sign-in page on first use. Check the editor's MCP log for the link and open it by hand. If a stale sign-in is stuck, delete the ~/.mcp-auth folder and reload the server.
Other assistants
Steps checked 2026-11-16. Clients change their menus often; if a step looks different, the server URL and the sign-in stay the same.
