Ask your SEO data.
Know what to do next.
Connect Claude, Cursor, or any MCP client to your Serpwise workspace. Your assistant answers from rankings, Search Console trends, AI visibility runs, opportunities, briefs, and digests — read-only, org-scoped, and live in minutes.
Connect Claude, Cursor, or any MCP client to your Serpwise workspace. Your assistant answers from rankings, Search Console trends, AI visibility runs, opportunities, briefs, and digests — read-only, org-scoped, and live in minutes.
Every signal Serpwise tracks, one question away.
Serpwise turns recommendations into prioritized fixes ready to deploy, so the work does not stop at another report.
Opportunities & rankings
Ask for the AI-detected opportunities on any domain — striking-distance keywords, lost positions, keyword cannibalization, rankings that never convert — and get the prioritized list, not a dashboard tour.
Search Console, summarized
Top pages, top queries, and this week's movers — pulled from your connected Search Console data and answered inside the conversation.
AI visibility, briefs & digests
Query your AI visibility runs — brand mentions, position, sentiment, competitors — plus the Site Brief and weekly digest, straight from the platform that produces them.
Connected in under a minute.
Create an API key
In your Serpwise dashboard, create an organization API key with the mcp:read scope. That is the only permission the connection ever gets.
Add the MCP server
Point Claude, Cursor, or any MCP client at cloud.serpwise.ai/api/mcp with your key. One command, nothing to install.
Ask in plain language
“Which keywords are in striking distance on my domain?” Your assistant queries your live workspace data and answers from it.
Revoke anytime
Rotate or delete the key in the dashboard and access ends immediately. Serpwise never grants write access through MCP.
From dashboard digging to direct answers.
Built to answer, not open another tab.
Analytics MCP gives your assistant read-only access to your Serpwise workspace, so answers come from your own data — and access is revocable at any time.
From GSC wrappers to the platform's own intelligence.
Wrap public Search Console data and stop there.
Every question costs a login, three filters, and an export.
Serves its own edge intelligence — opportunities, AI visibility, briefs — to the assistant you already use.
Before you
connect Claude.
01 Which MCP clients work with Serpwise? + −
Any client that speaks the Model Context Protocol over HTTP: Claude, Claude Code, Cursor, and others. Add https://cloud.serpwise.ai/api/mcp with your API key and the tools appear in your assistant.
02 Can the assistant change anything in my account? + −
No. The endpoint accepts keys with the mcp:read scope only. Your assistant can query domains, opportunities, Search Console summaries, AI visibility runs, and digests — it can never write, deploy, or configure anything.
03 Is my data isolated from other organizations? + −
Yes. Every request is scoped to the organization the API key belongs to. You only ever see your own workspace, and keys are revocable from the dashboard at any time.
04 How is this different from chat SEO tools or GSC wrappers? + −
Those tools re-fetch public data and stop there. The Serpwise Analytics MCP serves the intelligence the platform itself produces — AI-detected opportunities, AI visibility runs, the Site Brief, your weekly digest — alongside Search Console summaries.
05 Is this the same as the MCP Server feature for my website? + −
No. The MCP Server feature makes your website queryable by AI agents. Analytics MCP works the other way: it connects your own assistant to your Serpwise workspace data, so you can ask questions about your SEO performance.
Ask your SEO data a question.
Create an API key, add one MCP server, and your assistant answers from your live Serpwise workspace. Read-only, org-scoped, revocable anytime.