Click Decay

Compare Google Search Console CTR between two periods, split a click change into impressions and CTR, project clicks at a CTR and check known Search Console reporting issues. Every number is labelled observed, calculated or modelled. Hosted, read-only, no API key.

View on clickdecay.com

Hosted MCP Server

npx add-mcp 'https://clickdecay.com/mcp'

Installs into Claude Code, Codex, Cursor and more

Documentation

Click Decay MCP server

Click Decay's CTR calculations as a free MCP server. Add one address to Claude, ChatGPT, Cursor, VS Code or another MCP client and work through your Search Console numbers in the chat.

Address

https://clickdecay.com/mcp
  • Streamable HTTP with plain JSON responses.
  • No account, no API key and no sign-in.
  • Every tool only reads: nothing is stored, passed on or published.

Connect your assistant

Claude Code

claude mcp add --transport http clickdecay https://clickdecay.com/mcp

Claude on the web or desktop

Open Settings, then Connectors, and add a custom connector named Click Decay with the address above.

ChatGPT

Turn on developer mode in the advanced connector settings, then create a connector with the address above and no authentication.

Cursor

Add this to .cursor/mcp.json:

{
  "mcpServers": {
    "clickdecay": {
      "url": "https://clickdecay.com/mcp"
    }
  }
}

VS Code

Add this to .vscode/mcp.json:

{
  "servers": {
    "clickdecay": {
      "type": "http",
      "url": "https://clickdecay.com/mcp"
    }
  }
}

Any other client that supports Streamable HTTP connects with the same address.

Tools

  • compare_ctr_periods compares clicks, impressions and CTR of two periods of the same length, splits the click change into a part from impressions and a part from CTR, and checks the dates against known Search Console reporting issues.
  • project_clicks_at_ctr gives the clicks a number of impressions would earn at a CTR you choose.
  • impressions_needed_for_clicks gives the impressions a click target needs at a CTR you choose.
  • check_gsc_reporting_issues lists the known Search Console reporting issues that overlap your dates, with Google's own source.

The tools use the same calculation engine as the CTR calculator. The formulas and the known issues are in the methodology.

Example prompts

  • “Compare 1–28 August, 5,400 clicks from 120,000 impressions, with 1–28 September, 4,100 clicks from 124,000 impressions. How much of the drop came from CTR?”
  • “How many impressions do I need for 1,000 clicks at a CTR of 2.5%?”
  • “Were there known Search Console reporting issues between March and May 2026?”

How to read the results

  • Every number carries the label used across the site: observed, calculated, modelled or not established. See how the numbers are labelled.
  • CTR comes back as a fraction with its unit: 0.045 means 4.5%.
  • If a period overlaps a known reporting issue that affects impressions, every figure that depends on impressions is withheld and the issue is named with its source. Clicks are still compared.
  • The results do not show why clicks or CTR changed, or whether AI features played a part. Every comparison says so.

Privacy and limits

  • The tools accept numbers, dates and the name of the data source only: no queries, page URLs, site names or files. What your assistant sends is calculated in memory and answered. Nothing is stored or used for research.
  • The CTR calculator page calculates in your browser. The MCP server calculates on Click Decay's server, because your assistant sends it the numbers.
  • Search Console exports are still read only in your browser, on the analysis page. The MCP server takes no files.
  • About 60 requests a minute per connection. The details are in the privacy notice.

Registry and configuration files