Pricing, limits, and integration
Sorank's free MCP server is exactly that, free, and not gated behind the paid plan. You authenticate with a Google account over OAuth 2.1 with dynamic client registration for read-only Search Console access, so there are no API keys to issue or rotate and no per-call fee from Sorank. Google's own Search Console API quotas apply to the underlying data.
The paid platform is billed per website ($99 per site per month), not per API call, and its integration runs through CMS connectors and webhooks rather than a metered API. There is no published rate limit because there is no public REST API to rate-limit; the MCP tools are bounded by Search Console's limits and by the read-only scope of the granted Google access.
For an agent build, the practical pattern is: use the free MCP server to read Search Console performance, opportunities and history and to score pages with geo_score, and use webhooks plus the CMS connectors when you need content the paid autopilot generates to flow into your own systems. There is no way to drive article generation or backlink acquisition programmatically through a documented API today.
How much does the Sorank API actually cost?
No public API documented for Sorank.
- Programmatic access may be limited to enterprise contracts or unavailable entirely.
Which AI clients can read Sorank data?
Not every AI assistant supports MCP natively. Here's the per-client picture for Sorank specifically.
| Client | Support | Notes |
|---|---|---|
| Claude (Desktop/Web) | Native MCP | Add the MCP server URL and sign in with Google via OAuth; read-only Search Console access, no API key. |
| Claude Code | Native MCP | Connects to the same HTTP MCP server over OAuth 2.1. |
| Cursor | Native MCP | Documented setup; add the server URL and authenticate with Google. |
| Windsurf | Native MCP | Listed as a supported MCP client. |
| n8n | API-only (custom code) | No native node and no public REST API; integrate via webhooks and CMS connectors instead. |
Sorank also has an MCP server
If you're wiring Sorank into Claude / Cursor / Codex, the MCP server is usually less code than the REST API.
See Sorank MCP pageWhat you can build with the Sorank API
Three personas, three different shapes of build. Pick the row that matches how you actually ship.
Glue Sorank into your daily workflow
- Pull a digest of ranking changes into your morning Slack
- Trigger a one-off backfill when something looks off
- Pipe data into your own SQLite for ad-hoc queries
Sell Sorank reporting at scale
- White-label Sorank data into client-branded dashboards
- Run scheduled multi-account reports without logging into the Sorank UI
- Cross-reference with the rest of the client's stack (CRM, analytics, ad spend)
Production pipelines for Sorank
- Real-time sync into your warehouse via webhooks
- Custom alerts the dashboard's built-in alerting can't express
- Backfill + idempotency handling for Sorank data older than the dashboard exposes
Limits and gotchas
- No OpenAPI spec — you write typed clients by hand or use a third-party generator on the docs HTML.
- Webhooks available — react to Sorank events in real time instead of polling.
- No official SDK detected. Plan on hitting the API directly with your HTTP client of choice.
- Rate limits: always read the docs page before scaling — the published limit is usually lower than the practical one and overages can be expensive.
Agent-readiness verdict
There is no public REST API for the paid platform, which is the main limitation for programmatic use. Integration runs through CMS connectors, webhooks and GSC/GA4 connections. For most agent use the free MCP server is the better path anyway, but the missing REST API holds the API score to a 4 out of 10.
Sorank API FAQ
Does Sorank support webhooks?+
Should I use the API or the MCP server for Claude / Cursor / Codex?+
Does Sorank have a public API?+
Sources
- Sorank official site: https://www.sorank.com
10+ years in digital marketing. I review marketing software for AI-stack fit: real pricing, MCP and API support, and how cleanly each tool drops into an AI agent workflow, cross-checked against verified data and real user feedback.

