GROWTH PLAN · READ-ONLY · ONE SITE PER KEY
Claude Code, Cursor, and Codex can read the 15 reports SEO Receipts already stores for one site you own: Search Console performance for both windows, Site Check findings with their fix steps, page speed measurements, your task list, what each shipped change did, and Google indexing status.
NEEDS A CLIENT THAT SETS REQUEST HEADERS · SEE SETUP BELOW
EXAMPLE EXCHANGE
“Did the pricing page change work?”
CLICKS BEFORE
150
CLICKS AFTER
200
POSITION BEFORE
7.8
POSITION AFTER
6.1
Every response states its dates and where the numbers came from, and says that movement after a change is not proof the change caused it.
SAMPLE DATA
They read different data and are set up differently. Running both at once is fine and common.
FREE · SIGN IN WITH GOOGLE
Reads your Google Search Console account directly: clicks, impressions, CTR, average position, query and page rows, and sitemap status, for any property you allow. Six tools. Signs in with OAuth, so it works in Claude, ChatGPT, Cursor, and Codex.
Set up the free connectorGROWTH · ACCESS KEY
Reads what SEO Receipts has already checked and stored for one site: Site Check findings and their fix steps, page speed measurements, your task list, what each shipped change did afterwards, and indexing status. 15 reports. Authenticates with an access key, so it needs a client that sets request headers.
Set it up belowThree tools, 15 reports
Publishing one tool per report would put 15 descriptions into your assistant's context in every session. Instead it gets three tools and looks up the rest when it needs them.
seo_list_reportsLists every report with a one-line purpose. The assistant calls this first when it does not know the report id.
seo_describe_reportReturns a report's parameters, what it returns, and the cases it is the wrong choice for. Pass a check id to get that finding's fix steps instead.
seo_run_reportRuns one report against your site and returns structured JSON with the dates and sources included.
site_overviewsite_check_findingsfixed_findingssite_check_historycrawled_pagespage_speedevidence_bundlesearch_queriessearch_pagesquery_watchlisttodays_tasktask_backlogshipped_changeschange_detailindexing_statusONE ADDRESS · ONE ACCESS KEY
Create the key in the Workbench under “Let your assistant fetch fresh site data”. It is shown once. Paste it into the Authorization header below, replacing sr_agent_YOUR_KEY.
https://seoreceipts.com/api/agent/mcpCLIENT 01
Adds the server with the access key as a request header, in one command.
claude mcp add --transport http seo-receipts https://seoreceipts.com/api/agent/mcp \
--header "Authorization: Bearer sr_agent_YOUR_KEY"CLIENT 02
Add the server to your global or project mcp.json file.
{
"mcpServers": {
"seo-receipts": {
"url": "https://seoreceipts.com/api/agent/mcp",
"headers": {
"Authorization": "Bearer sr_agent_YOUR_KEY"
}
}
}
}CLIENT 03
Codex sets request headers in config.toml rather than on the command line.
[mcp_servers.seo_receipts]
url = "https://seoreceipts.com/api/agent/mcp"
http_headers = { "Authorization" = "Bearer sr_agent_YOUR_KEY" }Custom connectors there sign in with OAuth and give you nowhere to put a request header, so this connector cannot be added that way yet. The free Search Console connector uses OAuth and does work there.
Free connector setupEXAMPLE QUESTIONS
The assistant picks the report, reads the rows, and can act on them in the same session, because it already has your code open.
“Which of my pages lost the most clicks against the previous 28 days?”
“List the new findings from the latest Site Check and fix the top one.”
“Did the change I shipped to /pricing/ move anything? Show me the daily numbers.”
“How many of my known pages does Google report as indexed?”
“What is today's task, and what are the exact steps?”
“Which queries have more than 500 impressions and an average position past 10?”
What a key can do
An access key is created for a single site and cannot be pointed at another. No report accepts a site or account parameter, so there is no request an assistant can phrase that reaches data you did not grant.
The tool surface has no write, publish, or delete. Nothing an assistant does here changes your site or your account.
SEO Receipts stores a hash and a short prefix, never the key. Revoking one key leaves your other keys and your Google connection alone.
Sixty requests per minute per key, so a loop in an agent cannot run up your Search Console quota.
Responses are capped at 96 KB. When one is shortened, it names each shortened path and how many entries existed.
Read the full privacy policy and terms of service.
COMMON QUESTIONS
Not yet. Custom connectors there sign in with OAuth and have no field for a request header, and this server authenticates with an access key in the Authorization header. Use Claude Code, Cursor, or Codex, which all support headers.
The free connector reads your Google Search Console account directly and returns what Google returns. This one reads what SEO Receipts has already checked and stored for one site: Site Check findings, page speed measurements, tasks, shipped-change measurements, and indexing status. You can run both at once.
Check that the Authorization header contains the whole key, including the sr_agent_ prefix. A key is shown once when you create it; if you no longer have it, revoke that key in the Workbench and create another.
Every response carries an outputBudget field. When truncated is true, it lists which paths were shortened and how many entries existed, so the assistant can ask a narrower question. Site Checks also read a bounded number of pages, and each report states how many it read.
No. Every report is a read. There is no write, no publish, and no delete in the tool surface, and no report takes a site or account parameter, so a key can only ever reach the one site it was created for.
GROWTH PLAN · $29/MONTH
Growth includes the access keys for this connector, weekly Site Checks of up to 250 pages, fifty watched queries per site, and daily commentary on each new report.