Google MCP remote endpoint catalog
io.github.google/mcp
Overview
Catalog of Google-managed remote MCP endpoints documented for Google Cloud, Google, and Google Workspace products, plus source-review notes for the google/mcp examples repository.
Documentation
Overview
The google/mcp repository is Google's catalog for Google and Google Cloud MCP servers. Its README points to the Google Cloud supported-products page as the comprehensive list of Google-managed remote MCP servers in GA and public preview.
Remote Endpoint Coverage
This submission includes every concrete googleapis.com MCP endpoint currently listed in the supported-products table, including Data Lineage regional endpoints, Gemini Enterprise Agent Platform / Vertex AI toolset endpoints, and Google Workspace developer preview endpoints. Regional template URLs that contain a REGION placeholder are excluded because they are not runnable base endpoint URLs until a supported region is substituted.
Transport
Google-managed MCP servers are remote HTTP endpoints. Configure an MCP client with the endpoint URL for the product or toolset you want to use. Toolsets may expose separate endpoint paths and act as virtual MCP servers.
Authentication
Google and Google Cloud MCP servers follow the MCP authorization specification for HTTP-based transports. Depending on the product, clients can use Google OAuth credentials, Application Default Credentials, service accounts, agent identities, or API keys for services that document API-key support. IAM-protected Google Cloud endpoints require suitable IAM permissions, including mcp.tools.call through the MCP Tool User role or equivalent permission.
Configuration
Install and initialize the Google Cloud CLI, select or create a Google Cloud project, enable the product API, and configure your MCP client with the remote endpoint URL. For local ADC-based development, run gcloud auth application-default login; add OAuth scopes when the selected MCP server requires product-specific scopes. Configure each remote with transport streamable-http, the selected MCP endpoint URL, optional Authorization: Bearer ..., optional x-goog-user-project when your client or quota setup requires a project header, and X-Goog-Api-Key for endpoints that document API-key authentication such as Maps Grounding Lite and Developer Knowledge API.
Limitations
The repository itself is not an installable MCP server package. It is a catalog, guidance, and examples repository. Regional endpoint templates that include a region placeholder must be configured with a supported region before use. The repository states it is for demonstration purposes and is not an officially supported Google product. Individual remote endpoints can have separate launch stages, IAM requirements, scopes, toolsets, known issues, and product-specific limitations.