Search Console API vs MCP server: which one should a developer use?
· Organiq · third-party facts carry source and date in the text
Use the Search Console API when you write code that stores or transforms the data: REST with OAuth 2.0, 25,000 rows per call, 1,200 queries per minute per site. Use an MCP server when a model (Claude, ChatGPT, Cursor) should call the data during a conversation: Organiq exposes 44 tools, read-only Google access over Streamable HTTP with OAuth 2.1.

What is the Search Console API and what are its limits?
It is Google's REST interface to read search performance (the Search Analytics endpoint), inspect URLs and list sitemaps. Limits published by Google (developers.google.com/webmaster-tools/limits, October 30, 2026): Search Analytics, 1,200 queries per minute per site and per user, 30,000,000 per day and 40,000 per minute per project; URL Inspection, 2,000 per day and 600 per minute per site. Each call returns up to 25,000 rows ("batches of 25,000 rows at a time", API guide). Data covers 16 months (Google, 2018) and arrives 2 to 3 days late (Search Console Help). What stays on you: database, authentication, pagination, retries, schema and maintenance.
What is a Search Console MCP server?
MCP (Model Context Protocol) is the open protocol through which AI clients discover and call tools. Instead of you writing the query code, the model picks the tool and the arguments from the question. Google publishes the API; MCP servers for Search Console are built by third parties on top of it, Organiq among them, each with its own tool set, authentication and limits. Organiq exposes 44 tools, read-only Google access at https://organiqgeo.com/mcp (Streamable HTTP): summary, queries and pages, time series, CTR curve, quick wins (score_opportunities), decay, cannibalization, anomalies, forecast, AI traffic and report, with the analysis done on the server. OAuth 2.1 with PKCE: without a credential, a protected tool answers 401 with WWW-Authenticate: Bearer resource_metadata=… and the client opens the sign-in; 3 tools work before sign-in. Clients without OAuth use an API key (Authorization: Bearer org_live_…). Errors are JSON: { error: { code, message, nextStep, docsUrl } }; rate_limited carries retryAfterSeconds. Full reference at /docs.

When should I use the API, MCP, or both?
| Use case | Search Console API | MCP server (Organiq) |
|---|---|---|
| Keep history in your own data warehouse | Yes: you pull and store within the quotas | Indirect: Organiq already stores it daily; the tools read from that database |
| Ask in natural language in Claude, ChatGPT or Cursor | No | Yes: the model calls the tools in the conversation |
| Automated pipeline or CI | Yes | Yes, with an API key (for example claude -p in Claude Code) |
| Your own agent or script calling Organiq | — | Yes: JSON-RPC over HTTPS with the API key header, with any MCP client SDK |
| Export millions of raw rows | Yes, in batches of 25,000 | No: the tools return analyses and bounded lists, not dumps |
| Write to Search Console (submit a sitemap) | Yes, through the API | No: Google access is read-only |
| History beyond 16 months | Only if you stored it before | Yes, from the connection date (Starter and Agency plans) |
How does Organiq's MCP relate to the API?
Organiq is a consumer of the API: with the webmasters.readonly scope it syncs the connected properties once a day, within the quotas, and writes to its own database. The MCP tools read from that database, not from the API: your questions spend no Google quota, do not depend on the API being available at that moment, and see beyond the 16 months. Limits: newest data from D-3; only the properties of your account; no writes. Guide to the 16 months: Search Console history limit.
Frequently asked questions
Can I call Organiq's MCP from code, without an AI?
Yes. The endpoint is JSON-RPC over HTTPS (Streamable HTTP). Use an MCP client SDK or plain HTTP requests with the Authorization: Bearer header and your API key, created in the dashboard.
Does MCP replace the API for bulk export?
No. The tools return analyses and lists with row limits, designed for a conversation. For full dumps, use Google's API in batches of 25,000 rows.
Does Organiq have its own REST API?
Not as of October 30, 2026; only the MCP server. GSC Wizard offers a REST API (gscwizard.com/pricing, October 30, 2026).
Which authentication does the MCP server accept?
OAuth 2.1 with PKCE, dynamic client registration (DCR) and Client ID Metadata Documents, or a personal API key. Access tokens last 1 hour; refresh tokens 30 days, rotated on every use.
Do I need a Google Cloud project to use the MCP?
No. You sign in with your Google account in the Organiq dashboard and grant read-only access; the project and the API quotas are Organiq's. For the direct API, yes: your own project, credentials and per-project quotas.