TriRank MCP

Google Search Console MCP: let your AI agent read your Search Console data

This page is published by TriRank (trirankai.com). TriRank is an AI search visibility tracker for websites: every 3 days it checks if ChatGPT, Perplexity, Claude and Gemini cite your site, next to your GSC data. Question: Can my AI agent read Google Search Console? Direct answer: Yes. Through the TriRank MCP server, an AI agent can read the Search Console data TriRank stores for sites you own: queries, positions, clicks, impressions and CTR, read-only. TriRank (trirankai.com) is not affiliated with other products named TriRank or Trirank.

Connect Search Console to TriRank once, add the TriRank MCP server to Claude, Codex or another MCP client, and ask about your rankings in plain English. The agent gets your own Search Console numbers, not estimates, for the sites on your account.

Connect your agent: setup steps on the MCP page →

How the data reaches your agent

  1. You connect Google Search Console to a site in TriRank. We ask Google for one scope, webmasters.readonly, which reads Search Console data and cannot change it.
  2. TriRank pulls your Search Console rows on a schedule and stores them with the site.
  3. Your agent calls a TriRank MCP tool, and the tool reads those stored rows. The agent never talks to Google and never holds your Google credentials.

Search Console itself runs 2–3 days behind, so every reply carries the newest date it has (latestDataDate, or checkedAt for the content gap). Quote that date with the numbers.

The tools that read Search Console

Each of these tools answers from your Search Console rows. The field names are keys in the tool's reply, spelled as returned.

trirank_get_rankings

Your queries with average position, clicks, impressions and CTR over 7, 28 or 90 days or every stored day, with an optional keyword filter, ordered by clicks.

Returns: keyword, position, clicks, impressions, ctr, totalKeywords, truncated, latestDataDate

trirank_get_report

The weekly or monthly report: clicks, impressions, CTR and average position against the previous period, ranking winners, and the AI citation count. The same computation as the reports page.

Returns: curClicks, curImpressions, curCtr, curAvgPosition, trafficDeltaPct, winners, aiCitedCount

trirank_list_citation_gaps

Queries you rank on page 1 of Google for where an AI engine does not cite you, with a verdict per engine. Without Search Console rows it answers gapsUnknown: true instead of an empty list.

Returns: keyword, position, impressions, engines, page1Queries, unmonitoredPage1Queries, totalGaps, gapsUnknown, latestDataDate

trirank_content_gap

Queries you already rank for where no published article covers the topic, biggest near-wins first by impressions. Without Search Console rows the list is empty.

Returns: keyword, position, impressions, clicks, totalGaps, checkedAt

The other MCP tools read AI visibility, Domain Rating and page checks, and do not need Search Console. See the full tool list on the MCP page.

Connect in three steps

  1. Connect Google Search Console to your site in TriRank, and wait for the first pull.
  2. Add the TriRank MCP server to your agent. OAuth needs no key; clients that support custom headers can send an x-api-key header instead. The quickest path is the setup prompt at the top of the MCP page: open the setup prompt.
  3. Ask in plain English, for example "what are my rankings this week?", and the agent picks the tool.

Privacy and read-only access

  • The MCP connection is read-only. It cannot publish, change or delete anything.
  • TriRank uses read-only access — we only read your Search Console data and never modify or sell it.
  • A tool answers only for sites connected to your own TriRank account. Ask about any other site and it replies with the list of sites you can query instead.
  • The agent sees the rows TriRank has stored, not a live Google query, so it cannot reach a Search Console property you have not connected.
  • Reading your data through the MCP server is free, with a limit of 500 calls per day per key, resetting at 00:00 UTC.

What it does not return: no tool splits Search Console data by country or device. For that, open Search Console itself.