The ZeusSEO MCP connector reference: every tool your AI assistant can use

The ZeusSEO MCP connector gives your AI assistant more than 100 actions across the account you already use: Google Business Profile posting and reviews, Search Console, Analytics, rankings, crawls, audits, reports, and client records. This page is the complete reference: every tool group, what is free, the four billed actions, and how your data is protected.

If you have not connected it yet, start with the three-step walkthrough in the Google Business Profile MCP guide, then come back here to see everything else the same connection unlocks. The connector is included on every ZeusSEO plan and during the free trial, with nothing extra to buy.

One URL for everything

This is the only server address the connector ever uses. Everything below arrives through it, and every future tool will too, with nothing new to install:

You can also find this address, and generate or revoke access, inside ZeusSEO under Settings, in the Claude & ChatGPT section. There is no per-feature URL and no mcp.zeuseo.com subdomain; if you are ever handed a different ZeusSEO connector address, it is not ours. Setup itself takes about two minutes and is covered step by step in the GBP guide, the Search Console guide, and the Analytics guide. ChatGPT support is coming next and will use this same address.

Every tool the ZeusSEO MCP connector offers

Tools come in two kinds. A read tool looks at your data and changes nothing. A write tool changes something real, usually on a client's public Google profile, and a well-behaved assistant pauses to confirm before calling one. Every location, site, and report is shown to your assistant by your client's name, the custom name you set in the Clients module or the client's own listing or website name, never your agency or workspace name.

Google Business Profile: posts

List your connected locations and their published, scheduled, and not-yet-published posts, with an honest "not synced yet" flag so an unsynced zero is never mistaken for "this client is not posting" (read). Publish an update, offer, event, or alert post to one client or several; schedule single posts or bulk batches for future dates; edit or cancel a still-scheduled post; import posts from a CSV and export them back out; and upload a photo from a public image URL (write).

Google Business Profile: reviews, Q&A, and messages

List a location's reviews and the questions on its profile (read). Reply to a review, edit or delete an existing reply, and post answers to profile questions (write). Customer messages can be listed for context (read).

Google Business Profile: listing, services, attributes, and social links

Read a listing's profile, attributes, services, and social links (read). Update core listing fields including the business name, set attributes, update services, and set or replace social links (write). Renaming a business is the single riskiest edit here: Google can push a renamed listing back into re-verification. ZeusSEO measures how far the new name drifts from the current one and returns an explicit risk warning with every preview. The warning informs you; it never blocks you.

Google Business Profile: insights and post quality

Location insights and the search terms people used to find a listing (read). Fetch recent posts with their copy and images so your own AI can review quality for free, which is the default (read). Or run ZeusSEO's own post-quality engine, one of the four billed tools below (billed).

Search Console, read-only

List your verified sites, read the search performance overview, top queries, top pages, a single query's trend, performance by country and device, and a combined "what is wrong with my pages" view that joins visibility signals with the technical issues from your last crawl. This surface reports performance; it deliberately does not expose page indexation or URL-inspection status. The Search Console MCP guide shows it in action.

Google Analytics 4, read-only

List your GA4-connected sites, then read traffic overviews, sources, top and landing pages, conversions, engagement, demographics, technology, events, e-commerce, and any single metric's trend over time. Covered in depth in the Google Analytics MCP guide.

Olympus live dashboard, read-only

A portfolio summary across all your sites, a single site's overview, a single metric's trend, and ranked improvement opportunities.

Keywords, rankings, crawls, and audits

Metis lists your tracked keywords and related terms already in your Keyword Brain (read), adds keywords to tracking (write), and can run live keyword research against a paid provider (billed). Nike reads your rank overview, single-keyword positions, and visibility trend (read), and can run a live SERP competitor check (billed). Argus exposes crawl status, crawled pages, page detail, and crawl stats (read). Kronos runs a free technical audit and reads its results and issues.

Reports and clients

List saved reports and scheduled deliveries, list and read the clients you manage, and read a site's on-page SEO issues (read). Rename a client, assign locations, toggle managed status, set per-client AI instructions, and manage client notes, tasks, documents, and gallery items (write). Daedalus can list templates and read a report summary (read), then generate a report, create a share link, or schedule a delivery (write).

Notifications, project management, social, and account

Hera lists notifications and marks them read. Hermes lists tasks and sprints and can create or update tasks. The social reconcile tools compare a client's social profiles between their Google Business Profile and Search Console and can write the GBP side; the finder that proposes missing profiles has an optional paid lookup (billed). Workspace tools read your plan, Stater balance, usage history, and members. The AI-answer brand radar lists the prompts you track; its measurement tools honestly return "no data yet" until the measurement pipeline is live, rather than inventing a number. And a ticket tool files a "the connector could not do X" request straight into ZeusSEO.

What it cannot do, by design

• See or export your Google password or the underlying Google access token. That never leaves ZeusSEO's server.
• Publish the literal instant you ask. Posts go through the same queue as everything in ZeusSEO and typically go live within a few minutes.
• Upload a photo from your device. It needs a real, publicly reachable image URL, not a local file.
• Check whether a page is indexed by Google. There is no URL-inspection tool.
• Touch billing, payment methods, or subscription settings. It can read your plan and balance; it cannot buy, upgrade, or charge anything.
• See or act on any ZeusSEO account other than yours, or any client not connected to your account.
• Invent a number. Every read tool that has no data says so instead of filling the gap with a plausible-looking figure.

Your AI is free; ZeusSEO's paid engines are billed

Here is the money question, stated plainly. When Claude writes a post, decides which clients match "restaurants," or summarizes your reports, that thinking runs on your own Claude subscription, and ZeusSEO charges you nothing for it. The ZeusSEO actions themselves, publishing, scheduling, replying, reading your Google data, are already included in your plan and cost zero Staters through the connector. Exactly four tools are the exception, because they run ZeusSEO's own paid engines:

Each of the four states its exact cost and asks for your agreement before running, and each has a free alternative right next to it: let your own AI review the posts, read the keywords you already track, read the rank data ZeusSEO already stored. Every connector action, free or billed, is recorded in Credits, under History, tagged as an agent action so you can tell assistant-driven work from your own clicks. How Staters work across the whole platform is covered in the Staters guide. On a free trial one fair-use limit applies: 100 connector actions for the whole trial. A paid plan removes it.

Permissions, data, and privacy

The connector acts through the same Google connection you already set up inside ZeusSEO; there is no new Google permission screen. The flow is always the same: you type a request to your assistant, the assistant calls the connector with one specific action, ZeusSEO's server checks that your account is authorized for that client, performs the action using the Google access token it already holds, encrypted and server-side, and replies with the data or a plain confirmation. For reads, ZeusSEO serves its own cached copy first and only calls Google on a cache miss.

Your assistant never receives your Google token. Claude only ever talks to ZeusSEO, and ZeusSEO is the only thing that talks to Google. Your assistant also cannot act as a different account: which ZeusSEO account a request applies to is taken only from the credential ZeusSEO issued to your assistant, and no tool accepts an account or workspace id as an argument, so no wording in a chat can redirect an action onto someone else's clients. ZeusSEO never sees your broader chat conversation, only the specific action requests the assistant forwards. The full policy, including the connector-specific disclosure, lives in our Privacy Policy and Terms, and you can always reach us through the contact page.

Revoking is two independent switches: remove ZeusSEO from your assistant's Connectors settings, or revoke the credential inside ZeusSEO under Settings. Revoking stops future assistant actions without disconnecting Google from ZeusSEO and without deleting anything already done.

Safety: writes touch a real client's public profile

Roughly a third of the connector's tools write, and many change what a real client's customers see on Google. So nothing is built to publish silently:

• The assistant proposes; it does not assume. Write tools refuse a free-typed business name and require a resolved listing id, so "the downtown location" can never quietly become the wrong client. Before any write that touches several clients, ask your assistant to list the exact targets by name, and do not approve until it does.
• Preview before publish. The riskiest writes support a preview call that changes nothing and returns a plain-language summary of exactly what would change and exactly which clients it would touch. Use it.
• Write tools are marked sensitive. Following the MCP convention, publish, reply, and edit tools are not marked read-only, so Claude is expected to pause and ask you before calling them.
• Publishing is queued, not instant, and that is a feature. A post created through your assistant lands in the same queue as every ZeusSEO post, visible and editable from your ZeusSEO Calendar before it reaches Google. You can also require your client's own approval in the client portal before a post can go live.
• Results are honest about Google's real state. Google reviews posts asynchronously and can reject one minutes later; the connector reports the real state rather than claiming success on a bare acknowledgement. Failures are surfaced and notified, never silently dropped.
• A lapsed plan does not lose your work. If your subscription is past due, a live publish is parked in a hold that auto-publishes when your subscription resumes, so you never repost and end up with duplicates. To resume, see zeuseo.com/pricing.

Want to see it working end to end first? Start with getting started with ZeusSEO, or read why this route needs no Google API application of your own in Google API vs MCP.