Google products as MCP servers for Claude Code, Codex, OpenCode and Antigravity

What this is

google-services-mcps is a suite of Model Context Protocol servers for Google products. Each product is one plugin in one marketplace, and each plugin runs one local MCP server with the same name. The agent starts the server over stdio, the server calls Google's APIs with the credentials you give it, and every tool name starts with mcp__plugin_<product>_, so a call always traces back to one product.

The same servers run in four harnesses. Claude Code installs them as plugins from the google-services-mcps marketplace. The gsm installer writes the same servers into a Codex, an OpenCode or an Antigravity configuration. There is no build step and no server of the suite's own: the servers run on your machine, as you.

One plugin per product

A single plugin for every Google API would load thousands of tool definitions into every session. This suite splits the work by product instead, so you install only what you use.

• Install only what you use. Each plugin adds its tools to your session. Fewer plugins means less to load.
• Each product has its own login group. Products in one group share one login. A Search Console login does not reach Gmail.
• Switch one server off for a session. Use /mcp to turn a server off and on again without uninstalling it.
• Tool names show the product. Every tool name starts with mcp__plugin_<product>_, so a call always traces back to one product.

The 23 products

Each product id is also its plugin name and its server name. The cards below are generated from the plugin folders at build time, and each one links to the product's page with its tools, its scopes and its login group.

• Workspace Admin

  gadmin

  Google Workspace administration: Cloud Identity, Chrome management and policy, Groups Settings, licensing, reports, alerts, Vault, reseller and Cloud Search admin.

  368 tools · workspace-admin login

• Ads and Publisher

  gads

  Google Ads API (accounts, campaigns, ad groups, ads, keywords, budgets, conversions, assets and GAQL reporting, with every other method through the gateway), plus advertising and publisher APIs: Search Ads 360, Display & Video 360, Campaign Manager, Ad Exchange, AdSense, AdMob, Real-time Bidding and more.

  338 tools · business login

• AI and ML

  gai

  Generative and classic AI APIs: Discovery Engine, Vertex AI, Dialogflow, Vision, Speech, Translate, Document AI and agent services.

  364 tools · cloud login

• Google Analytics

  ganalytics

  Google Analytics admin and data APIs for GA4 properties, configuration and reports.

  83 tools · business login

• Apps Script

  gapps

  Apps Script projects and execution, plus the Workspace Marketplace SDK.

  26 tools · workspace-user login

• Business Profile

  gbusiness

  Business Profile accounts, locations, verifications, lodging, place actions, notifications and performance.

  59 tools · business login

• Google Calendar

  gcalendar

  Google Calendar calendars, events and calendar settings.

  55 tools · workspace-user login

• Google Chat

  gchat

  Google Chat spaces, messages and members, plus Workspace Events subscriptions.

  78 tools · workspace-user login

• Google Classroom

  gclassroom

  Google Classroom courses, coursework, submissions, students and teachers.

  129 tools · workspace-user login

• Google Cloud

  gcloud

  Google Cloud console APIs: projects, service enablement, API keys, billing, monitoring, storage, BigQuery and IAM, plus the rest of the infrastructure, data, devops, networking, security and governance APIs.

  393 tools · cloud login

• Contacts and Profile

  gcontacts

  Google Contacts and People, personal health metrics, Data Portability, and the OAuth2 userinfo endpoints.

  75 tools · workspace-user login

• Google Drive and Docs

  gdrive

  Google Drive files, labels and activity, plus Docs, Sheets, Slides, Forms and Books.

  200 tools · workspace-user login

• Firebase

  gfirebase

  Firebase management, App Check, App Distribution, Crashlytics, Hosting, Data Connect, Rules, Test Lab, FCM and Identity Toolkit.

  315 tools · developer login

• Gmail

  gmail

  Gmail mailboxes, messages, labels and settings, plus Gmail Postmaster Tools.

  114 tools · workspace-user login

• Maps and Location

  gmaps

  Maps Platform and location APIs: Places, Address Validation, Solar, Air Quality, Pollen, Street View Publish and related datasets.

  39 tools · apikey login

• Google Meet

  gmeet

  Google Meet spaces, conference records, participants and recordings.

  34 tools · workspace-user login

• Merchant Center

  gmerchant

  Merchant Center: Merchant API and Comparison Shopping Service, through a service account key.

  153 tools · service-account login

• Google Play

  gplay

  Google Play developer publishing and reporting, Play Games Services, Android Enterprise and Management, Play Integrity and device APIs.

  366 tools · service-account login

• Search Console

  gsc

  Search Console sites, sitemaps, search analytics, URL indexing and site verification.

  37 tools · searchconsole login

• Search and Web Quality

  gsearch

  Public search and web-quality APIs (Custom Search, PageSpeed, CrUX, Safe Browsing, Web Risk, Fact Check) that take an API key instead of OAuth. The Custom Search JSON API is closed to new customers and is scheduled to be discontinued on 2027-01-01.

  53 tools · apikey login

• Tasks and Keep

  gtasks

  Google Tasks task lists and tasks, plus Google Keep notes.

  29 tools · workspace-user login

• Tag Manager

  gtm

  Google Tag Manager accounts, containers, tags, triggers and variables.

  118 tools · business login

• YouTube and Blogger

  gyoutube

  YouTube Data, YouTube Analytics and YouTube Reporting APIs, plus Blogger.

  132 tools · business login

How the pieces connect

The marketplace lists the plugins. A plugin holds one MCP server, a consent hook for Claude Code, a tool map and a skill. The server reads your tokens from the token directory and calls Google over HTTPS. The hook runs before each tool call and asks before a change.

Codex, OpenCode and Antigravity have no approval hook in this suite. A client that cannot ask for approval is refused every change, so nothing runs without a confirmation. The full model is on the architecture page.

Install

One command installs the suite and Gmail for Claude Code. It adds the marketplace and installs the gmail plugin for your user account, the default scope. It checks what Claude Code needs first and writes nothing until that is in place.

npx google-services-mcps install --agent claude --plugin gmail

Run the command with no arguments in a terminal to open a guided menu instead. The menu asks for the agent, the products and the scope, shows the exact command it will run, and previews it with --dry-run. Every route and every flag is on the install page.

Safe by default

The controls apply in order, and one failing layer does not let a change through.

1. Token scopes. A login asks only for the scopes of its profile: readonly (the default), readwrite, full, or an exact list. Google rejects any call outside them.
2. Tool registration. A write or destructive tool is listed only when Allow write tools is on. It is off by default.
3. Approval gate. In Claude Code a PreToolUse hook asks before every change. The hook never allows a call, so your own permission rules still apply. Destructive actions ask twice: once in the hook and once in an Approve this action? form.
4. Confirmation setting. every-change is the default. destructive-only asks only before deleting, sending, sharing, publishing and the other destructive actions. off asks for nothing, and deny rules still apply.
5. Policy file. policy.json in the token directory holds allow, ask and deny rules. A matching deny always wins.
6. Audit log. Each gated action writes one JSON line with the time, tool, method, decision and outcome, and a hash of the arguments, never the values.

The configuration page lists the settings by name, and the troubleshooting page covers the messages the suite prints.

Status

The suite is in beta. The code is built and tested offline: the unit and build tests pass, a smoke test starts all 23 servers over stdio, and Claude plugin validation passes for the marketplace and the Gmail plugin. Live Google accounts have been tested for three products only: gcloud (the project readiness check and enabling APIs), gsc (reads and a live login check) and gmail (reads, on six accounts). Nothing else has run against a real account, and no mail has been sent.

Test one product at a time, starting with a read, on an account where a mistake does no harm. The quick start walks through the first server.

Questions

The FAQ answers the questions people ask most: what it costs, which accounts are needed, whether data leaves your machine, and how this compares with Google's own MCP servers.

The project is independent and is not affiliated with Google. It is licensed under the Apache License, Version 2.0.