Rank by Ouroboros Apps
Read Google Search Console SEO data and inspect URLs through MCP clients.
List verified Search Console properties.
Get top queries and top pages with clicks, impressions, CTR, and average position for a date range.
View daily performance trends for clicks, impressions, CTR, and position.
Compare totals between two periods and see differences derived from those totals.
Find quick wins: high-impression, low-CTR queries.
Find dropped pages where position worsened, clicks fell, or pages disappeared.
Inspect a URL's Search Console status, including verdict, coverage, and last crawl.
Check account status: Google connection, trial end, and Pro access.
Use it from ChatGPT, Claude, Gemini, Grok, Cursor, or other MCP clients via Streamable HTTP and OAuth.
Allows querying Google Search Console data for verified properties, including top queries and pages, daily performance trends for clicks, impressions, CTR, and average position, period comparisons, quick-win opportunities, dropped pages, and URL Inspection status.
Integrates Stripe for subscription billing, enabling Checkout for monthly or yearly plans and webhook handling for subscription status.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Rank by Ouroboros Apps show my top Google Search queries from the last 28 days"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Rank by Ouroboros Apps
Rank by Ouroboros Apps answers SEO questions from the Google Search Console account you connect. It is for site owners, bloggers, small businesses, and SEO freelancers who want those numbers inside ChatGPT, Claude, Gemini, Grok, Cursor, or any other MCP client that speaks Streamable HTTP and OAuth.
The assistant can list verified properties, read top queries and pages, follow clicks, impressions, CTR, and average position over time, compare two periods, find queries with high impressions and low CTR, see pages that dropped, and check URL Inspection status. Every metric comes from the Search Console API response. Rank does not estimate traffic or fill in days the API left out. CTR stays the fraction Search Console returned (0.02 is 2%).
A 14-day trial starts when you connect Google. After that, Pro is a Stripe subscription. The amount is shown at Stripe Checkout, not in this README or the product.
Hosted server
MCP server URL:
https://rank.ouroborosapps.com/mcp(Streamable HTTP, OAuth sign-in)Status: early access. Paste the URL into Claude, Cursor, Grok, or ChatGPT developer mode.
Registry name:
io.github.LAHutchins91/rank
Related MCP server: Google Search Console MCP Server
Connect an assistant
The MCP address is https://YOUR_HOST/mcp after deploy, or http://127.0.0.1:44721/mcp when you run it locally. Choose OAuth and leave the client id and secret empty. Rank supports dynamic client registration and PKCE.
Cursor, in ~/.cursor/mcp.json:
{
"mcpServers": {
"rank": {
"url": "http://127.0.0.1:44721/mcp"
}
}
}Claude Code:
claude mcp add --transport http rank http://127.0.0.1:44721/mcpUse the same URL for ChatGPT, Claude, Gemini, and Grok. The in-app connect page repeats these steps for the host in APP_BASE_URL.
Tools
list_properties— verified Search Console propertiestop_queries— queries for a date rangetop_pages— pages for a date rangeperformance_trends— daily clicks, impressions, CTR, and positioncompare_periods— totals for two ranges, plus differences labeled as derived from those totalsquick_wins— queries at or above an impression threshold and at or below a CTR thresholddropped_pages— pages whose position worsened, whose clicks fell, or that disappeared from the current responseinspect_url— URL Inspection API resultaccount_status— whether Google is connected and whether the trial or Pro subscription is active
If you omit dates, Rank uses a 28-day window ending three UTC days ago and says so in the result. Pass startDate and endDate (YYYY-MM-DD) to choose the window.
Google Cloud OAuth client
Create an OAuth client of type Web application. Rank reads:
GOOGLE_CLIENT_IDGOOGLE_CLIENT_SECRET
Authorized redirect URI, exactly, with no trailing slash on the origin:
${APP_BASE_URL}/google/callbackLocally, with the default APP_BASE_URL, that is:
http://127.0.0.1:44721/google/callbackAdd these scopes on the OAuth consent screen:
openidhttps://www.googleapis.com/auth/userinfo.emailhttps://www.googleapis.com/auth/webmasters.readonly
webmasters.readonly is the Search Console read-only scope. Rank requests offline access so Google returns a refresh token. The refresh token is encrypted before it is stored. TOKEN_ENCRYPTION_KEY is the key (a long random string). If the key changes, existing tokens cannot be read and the account has to connect Google again.
If the Google console asks for an authorized JavaScript origin, use the origin of APP_BASE_URL (http://127.0.0.1:44721 locally). The redirect URI above is the value that must match.
Storage
Trial state, Stripe customer ids, MCP OAuth clients and tokens, pending Google sign-in, and the encrypted Google refresh token share one storage interface. Set STORAGE_BACKEND:
Backend | When | What it uses |
| local experiments and tests | data disappears when the process stops |
| a single long-running server or Docker volume |
|
| Vercel | one private Blob at |
| a Postgres database you already run |
|
Postgres uses one table, created on first use if it is missing:
CREATE TABLE IF NOT EXISTS rank_kv (
collection text NOT NULL,
id text NOT NULL,
document jsonb NOT NULL,
PRIMARY KEY (collection, id)
);There is no second schema. Memory and file storage reset on Vercel, so production uses the Blob backend. The Blob document uses the same layout as the file store: collections of JSON records. OAuth authorization codes and pending Google sign-in state are records in that document, so a callback can land on a different serverless instance. Each write drops expired auth codes, pending sign-in sessions, access tokens, and refresh tokens. BLOB_READ_WRITE_TOKEN is injected when the Vercel Blob store is connected. Do not commit it.
Billing
Set these from the Stripe account Lawrence already uses. Do not create products in this repo. The price ids are not dollar amounts.
STRIPE_SECRET_KEYSTRIPE_PRICE_MONTHLYSTRIPE_PRICE_YEARLYSTRIPE_WEBHOOK_SECRET
Checkout is POST /billing/checkout with { "plan": "monthly" } or { "plan": "yearly" }. The webhook is POST /billing/webhook. GET /health includes billingConfigured: true only when the secret key and both price ids are set.
The local trial is 14 days from the first Google connection. Checkout sends Stripe the whole days still left in that trial, when any remain, so the first charge waits until the trial is over.
Run locally
npm install
cp .env.example .env
# fill Google, encryption, and Stripe values in .env
npm run devThe server listens on PORT (default 44721).
npm test
npm run typecheck
npm startnpm start runs the compiled server. Docker builds the same command (node dist/src/server.js) and expects logo.jpg at the image root.
Deploy
Vercel: set APP_BASE_URL to https://rank.ouroborosapps.com, set STORAGE_BACKEND=blob, and connect a Blob store so Vercel injects BLOB_READ_WRITE_TOKEN. vercel.json sends every path to the Node function and bundles logo.jpg into that function. /logo.jpg and the app routes are served by the function. /package.json is not a static file. The remote in server.json is https://rank.ouroborosapps.com/mcp.
The registry name is io.github.LAHutchins91/rank. The icon is https://rank.ouroborosapps.com/logo.jpg.
Environment variables
Variable | Required for |
| public origin; determines the Google redirect URI |
| listen port, default |
| Google sign-in and Search Console |
| Google token exchange |
| encrypting refresh tokens and signing the browser session |
|
|
| file backend path |
| blob pathname, default |
| Vercel Blob read-write token, injected on Vercel |
| postgres backend |
| Checkout and the billing portal |
| monthly Checkout price id |
| yearly Checkout price id |
| Stripe webhook signatures |
| public contact on the site; default |
RANK_TEST_HOOKS=1 lets tests complete MCP login without Google. The process refuses to start when that is set and NODE_ENV=production.
Support
Privacy questions, account deletion, and a copy of the account record go to ouroborosplugins@gmail.com. Do not send passwords, OAuth tokens, API keys, or payment card details. The same address is on the privacy and support pages. To disconnect Google, revoke Rank at https://myaccount.google.com/permissions.
License
MIT. Copyright (c) 2026 Lawrence Hutchins.
More from Ouroboros: https://ouroborosapps.com
Available Tools
9 toolsaccount_statusAccount statusARead-onlyIdempotentInspect
Whether Google Search Console is connected, when the 14-day trial ends, and whether Pro access is active. Does not query Search Console and does not include a price.
Inputs: no named parameters. Returns: data
compare_periodsCompare periodsBRead-onlyIdempotentInspect
Compare two date ranges using the Search Console totals for a property (no dimension grouping). Reports both API metric objects. Differences are labeled as derived from those returned numbers. Omit compare dates to use the previous window of the same length.
Inputs: siteUrl (required), device, country, endDate, +4 more. Returns: data
dropped_pagesDropped pagesBRead-onlyIdempotentInspect
Pages whose Search Console position got worse, whose clicks fell, or that disappeared from the current response. Does not invent zeros for pages the current response omitted.
Inputs: siteUrl (required), limit, device, country, +5 more. Returns: data
inspect_urlInspect URLBRead-onlyIdempotentInspect
URL Inspection status for one URL on a property you can access. Returns the Search Console inspection response, including verdict, coverage, and last crawl fields when the API sent them.
Inputs: siteUrl (required), inspectionUrl (required), languageCode. Returns: data
list_propertiesList propertiesARead-onlyIdempotentInspect
List the Search Console properties on the connected Google account. Returns siteUrl and permissionLevel exactly as the sites.list API returned them.
Inputs: no named parameters. Returns: data
performance_trendsPerformance trendsBRead-onlyIdempotentInspect
Daily clicks, impressions, ctr, and position for a property. Each row is a date Search Console returned. Missing dates are not filled in, and ctr is the API fraction.
Inputs: siteUrl (required), device, country, endDate, +2 more. Returns: data
quick_winsQuick winsARead-onlyIdempotentInspect
Queries with high impressions and low ctr in Search Console. Defaults are at least 100 impressions and ctr at or below 0.02 (the API fraction, so 0.02 is 2%). Does not estimate missed clicks.
Inputs: siteUrl (required), limit, device, maxCtr, +5 more. Returns: data
top_pagesTop pagesBRead-onlyIdempotentInspect
Top pages for one property and date range. Metrics are copied from Search Console rows. ctr is the API fraction from 0 to 1. Omit dates to use the default 28-day window.
Inputs: siteUrl (required), limit, device, country, +3 more. Returns: data
top_queriesTop queriesARead-onlyIdempotentInspect
Top search queries for one property and date range. clicks, impressions, ctr, and position are copied from Search Console. ctr is a fraction from 0 to 1, not a percent. Omit dates to use the default 28-day window.
Inputs: siteUrl (required), limit, device, country, +3 more. Returns: data
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 9 tools
Each tool targets a distinct analysis or resource: listing properties, top queries/pages, URL inspection, trends, period comparison, quick wins, dropped pages, and account status. The purposes are clearly differentiated with no overlap, so an agent can easily select the right tool.
All tool names follow a consistent snake_case pattern, using noun compounds or adjective_noun structures (e.g., top_queries, inspect_url, performance_trends). The naming is predictable and readable throughout.
With 9 tools, the set is well-scoped for a Google Search Console analysis server, covering core reporting and inspection tasks without redundancy. Each tool earns its place and the count is within the ideal 3-15 range.
The tools provide strong coverage for common GSC analysis: listing properties, top queries/pages, trends, comparisons, quick wins, dropped pages, and account status. Minor gaps exist, such as the ability to filter or segment queries/pages by device or country, but the core lifecycle is well addressed.
Related MCP Connectors
Google Search Console for AI assistants: traffic, rankings, indexing and page checks. Read-only.
SEO & marketing toolkit for AI agents: GA4, Search Console, AdSense, GTM, PageSpeed, Trends.
Google Search Console in your AI: overview, opportunities, index gaps, page checks, long history.
Google Search Console, GA4 and Bing Webmaster data for SEO and AI-search work. 20 read-only tools.
Related MCP Servers
- AlicenseAqualityDmaintenanceProvides read-only access to Google Search Console data, allowing AI assistants to query site performance metrics like keywords, clicks, and rankings using natural language. It supports listing verified properties, querying search analytics with dimension filters, and retrieving sitemap information.31MIT
- AlicenseAqualityDmaintenanceConnects Google Search Console to AI assistants, enabling natural language analysis of SEO data. Provides read-only tools for properties, search analytics, URL inspection, and sitemaps.15MIT
- AlicenseAqualityDmaintenanceEnables AI assistants to query and manage Google Search Console data, including search analytics, URL indexing status, and sitemap management, for SEO and LLMO analysis directly from a conversation.156,899 npmMIT
- AlicenseAqualityDmaintenanceEnables AI assistants to analyze Google Search Console SEO data through natural language, including search analytics, URL inspection, sitemap management, and property management.21MIT