FAQ
Frequently asked questions
These are the questions the project's own documentation answers. Every answer is mirrored in the page's structured data, so a search engine reads the same text a person does.
The questions
Does it cost money?
The suite is free. Google's quotas, billing and approval rules apply to each call you make. Claude's own usage grows with each installed product, because every product adds tool definitions to the session. Install only the products you use.
Which Google accounts do I need?
A Google Workspace account is the main target. Each login group needs a Desktop OAuth client in a Google Cloud project. gadmin needs a super admin and a service account with domain-wide delegation. gsearch needs an API key. Personal accounts worked for Gmail reads in a live test on 2026-10-29; for the other products they are untested.
Is my data sent anywhere except Google?
As far as the source shows, the servers call only Google's API and OAuth endpoints, and the code has no separate telemetry path. Tokens stay in the token directory on your machine. Anything a tool returns, such as mail text, becomes part of the agent's conversation, so it goes to that agent's model provider as usual.
Can I use it with Codex, OpenCode or Antigravity?
Yes. Run npx google-services-mcps install --agent codex --plugin <id>, and change the agent name for the others. None of the three has an approval hook in this suite, and a client that cannot ask for approval is refused every change. How each one handles approvals has not been tested in a live session.
Why do I see approval prompts?
Changes and deletions ask by default, because confirmation is every-change. Destructive actions such as deletions, sends, shares and publishing also ask a second time, with an exact preview. To ask less, set Confirm before changes to destructive-only or off. Deny rules in policy.json still apply.
Why is a tool missing?
Usually one of these: Allow write tools is off, so write and destructive tools are hidden; the login uses the readonly profile, so the token lacks the write scopes; the server is switched off in /mcp; or the plugin is disabled. If the group is not logged in, the tool is listed but each call fails with a login message. Run npx google-services-mcps doctor --plugin <id> to check the install.
Why are there so many tools?
Google's APIs are large. Each plugin has a tool for many of the methods of its APIs, and generated tools are capped at 350 per plugin. Gateway tools reach the methods that have no tool of their own. Claude Code's tool search loads definitions when they are needed. To list fewer tools, set the plugin option toolset to google or curated.
How is this different from Google's official MCP servers?
Google runs MCP servers of its own for some products, and you can use them next to these. This suite adds changes with consent, several Google accounts per login group, personal Google accounts for Gmail reads, sending mail with two approvals, per-method tools for each product's main APIs, gateway tools for the rest, and no enrolment beyond a Desktop OAuth client in your own project. The project found no official MCP server for Search Console, Tag Manager, YouTube and Blogger, Google Play publishing, Business Profile, Meet, Tasks and Keep, Apps Script, or the Admin SDK; that comes from a search of Google's pages, so it is not proof.
Is this an official Google product?
No. It is an independent project and is not affiliated with, endorsed by or sponsored by Google. Google and the Google product names are trademarks of Google LLC.
Which licence applies?
The Apache License, Version 2.0 (Apache-2.0). Copies you pass on must include the LICENSE and NOTICE files, and changed files must say that they were changed. Contributions are under the same licence.
How do I remove everything?
Preview the removal with npx google-services-mcps uninstall --all --dry-run, then remove every install with --all --yes. Delete the token folder ~/.google-services-mcps by hand; no gsm command deletes it. Remove the marketplace with claude plugin marketplace remove google-services-mcps, then revoke the suite's access at myaccount.google.com/permissions.
What has been tested against real Google accounts?
Three products. gcloud: the project readiness check and enabling APIs, with an application-default login on a Workspace account. gsc: reads, and a live login check that found the login valid on 2026-10-29. gmail: reads on 2026-10-29, on six accounts, personal accounts among them. Nothing else has run against a real account, and no mail has been sent.
Why does a login ask for scopes I did not expect?
A login merges with the scopes the same account already holds for its group, so logging in for one product keeps the others. Name the account with --account to merge only that account's stored scopes. Use --replace to drop the stored scopes and keep only what the new login requests. A merge can leave write scopes from an earlier readwrite login in place.
What happens if Google throttles a call?
The suite retries throttled requests up to three attempts in all, with backoff. Only throttled requests are repeated: HTTP 429 and 503 for any method, and rate-limit 403s for reads only. A write is never repeated on a 403. After the last attempt, the error reaches the agent.
Can the agent see my tokens?
No. Tokens, the client file and the API key stay in the token directory, and the agent can list accounts by name, set the default and remove one, but never sees a token. Keys that look secret are redacted from prompts, logs and errors.
Still stuck?
The troubleshooting page has the exact messages and their fixes. The repository's issue tracker is the place for a bug report; include the product id, the agent, the command or tool name and the error text, and remove tokens, client secrets, API keys and account data first.