Persyst connector
Google Search Console MCP connector for ChatGPT, Claude and Copilot
Connected once with the Google account that owns the property, without inviting each user to Search Console.
Updated on October 11, 2026
Your tools
- By the admin or by each member
- Rights per person, team or client
- Who read what, and when
Everyone’s AI
In short
- Persyst works without a vendor MCP server: Google does not publish a Search Console connector for AI assistants, Persyst provides its own.
- Read-only: the connection only holds the webmasters.readonly scope. It cannot add a property, submit a sitemap or request indexing.
- A Search Console property is opened to a team, a client or a person; any other property stays invisible to their AI.
- The data is the Search Console API’s: 16 months of history, about two days of lag, anonymized queries omitted.
EXAMPLES
What your team can ask
Which queries gained the most clicks this month compared to last month?
Three queries drive the increase: “mcp sellsy” (+41 clicks), “connect search console to chatgpt” (+27) and “persyst” (+19). Home page impressions are up 18%, average position moved from 9.4 to 6.1.
Sources consulted
- Search Console · persyst.ai · 30-day comparison
Is the /connectors/sellsy page indexed?
Yes. Last crawled on October 9, canonical matches, no mobile errors. It is not yet listed in the declared sitemap: the submitted version predates its publication.
Sources consulted
- Search Console · URL inspection
- Search Console · declared sitemaps
HOW IT WORKS
Google Search Console in your AI, in three steps
Connect the property
Under Data sources, an administrator picks Google Search Console and signs in with the Google account that owns or is delegated on the property. Persyst only requests the read-only scope. The account’s properties are listed; the administrator selects which ones to share.
A member can also connect their own Google account under My connectors, to query their own properties without sharing them.
Open access
Each property is granted to a team, a client or a person, with the list of allowed tools. A member without access does not see the property in their assistant. Grants can be changed at any time and apply on the next call.
Ask from the assistant
The member asks their question in ChatGPT, Claude or Copilot. The assistant calls Persyst’s Search Console tools, which check the rights, query Google’s API and return the results. The history keeps who used which tool, and when.
TOOLS
What your assistant can do
Google Search Console· 5 tools
Opened team by teamLists the Search Console properties opened to the member, with no API call and no quota consumed.
list_gsc_sitesClicks, impressions, CTR and average position over a period, by query, page, country, device or date, up to three dimensions.
query_search_analyticsCompares two periods with deltas computed server-side, sorted by click gain.
compare_search_analyticsCrawl and index status of up to ten URLs, within the property’s Google quota.
inspect_urlsDeclared sitemaps with their status, warnings and, per sitemap, submitted and indexed counts.
list_sitemaps
Rights and audit trail
Rights per person, team or client.
Then, inside the tool, only the items you open. The rest does not exist for the AI.
One-click revocation.
Removing a member cuts their access in every AI at once.
A history.
Who used which tool, and when.
Credentials that stay put.
They remain encrypted in Persyst, never in the assistants.
COMPARISON
Persyst or a Google Search Console MCP server?
| Criterion | Persyst | Community Google Search Console MCP server |
|---|---|---|
| Who authenticates | The company once, or each member with their own account. | Each member, with their own API key. |
| Installation | None: a remote MCP server, authorized from the assistant. | A server to install and maintain on every machine, or a third-party service you hand the key to. |
| Where credentials live | Encrypted in Persyst, never in the assistant. | In each member’s assistant configuration. |
| Scope | Per person, team or client, then per opened item. | Everything the key allows. |
| History | Who used which tool, and when, for the whole team. | None, or machine by machine. |
| When a member leaves | One-click revocation, in every AI. | A key to revoke at the vendor, machine by machine. |
What this connector does not do
- No writes: no property added, no sitemap submitted or deleted, no indexing request.
- No site-wide indexing report: Google’s API only exposes inspection per URL, with a daily quota per property. Persyst never crawls a whole site.
- No Google Analytics, Google Ads or Bing Webmaster Tools data: each source has its own connector.
- No history beyond the 16 months Google keeps, and no same-day data.
Questions
Frequently asked questions
Is there an official MCP server for Google Search Console?
Persyst does not need one. It calls the Search Console API directly with the company’s connection and exposes its own tools to your assistant. If Google ever publishes an official connector, it will authenticate per user: Persyst would still be useful to open read access to those without access to the property.
Do I have to invite every member to the Search Console property?
No. Someone who owns the property connects their Google account once in Persyst. The members you authorize then read the data from their AI, without being invited as users of the property in Search Console.
Can an external SEO consultant use it for a single client?
Yes. You open that client’s property to that consultant, and only that one. The organization’s other properties do not appear in their assistant. Removing their access takes one click.
What does Google see of this usage?
Calls to the Search Console API with the authorized connection, within your account’s usual quotas. Persyst changes nothing on Google’s side.
How do I use it from ChatGPT or Claude?
Each member adds Persyst as an MCP server in their assistant and authorizes it once. The Search Console tools they are entitled to then appear in their conversations, next to their other Persyst tools.
