Cursor has fixed the issue with its desktop redirect URI and can be used with Google and Google Cloud MCP servers. To learn how to configure MCP servers for Cursor, see Client-specific guidance.

You can use the tool.name attribute to control access to specific MCP tools in your Identity and Access Management (IAM) allow and deny policies. For more information see Control MCP use with IAM.

Due to an authentication issue, Google and Google Cloud remote MCP servers can't be used with Cursor.

Our OAuth 2.0 client ID creation flow doesn't allow adding custom URI schemas like Cursor's callback URL, cursor://anysphere.cursor-mcp/oauth/callback, as redirect URLs.

Google and Google Cloud remote MCP servers are generally available (GA). Individual MCP servers might be in Preview or GA—to check the launch status of a product, search for the product in Supported products.

To learn more about what you can do with MCP servers, read 50+ fully managed MCP servers now available for Google Cloud services.

You can use Cloud Trace to get answers about your MCP server use, tool failures, and latency causes. To get started, see Use Cloud Trace to monitor MCP use.

The custom constraint gcp.managed.allowedMCPServices and organization policy control of MCP use is deprecated and will no longer work.

You can use Identity and Access Management deny policies to control MCP use. For more information, see Control MCP use with Identity and Access Management.

Change

Starting March 17, 2026, you no longer need to separately enable Model Context Protocol (MCP) servers. Remote MCP endpoints are available by default when you enable a supported product in your project. This update is rolling out gradually across regions.

After March 17, 2026, Google and Google Cloud remote Model Context Protocol (MCP) servers are automatically enabled when you enable a supported service.

Deprecated

The custom constraint gcp.managed.allowedMCPServices and organization policy control of MCP use is deprecated. If you created an organization policy to control MCP use prior to February 17, 2026, then it won't work after March 17, 2026. If you don't use the gcp.managed.allowedMCPServices constraint, then effective February 17, 2026, you aren't able to use it.

You can use Identity and Access Management deny policies to control MCP use. For more information, see Control MCP use with Identity and Access Management

Support for Model Context Protocol (MCP) use is available in Preview for select Google and Google Cloud services.

To see a demo and read about why we're offering remote MCP servers available over HTTP instead of local MCP servers, read Announcing official Model Context Protocol (MCP) support for Google services.

For more information, see Google Cloud MCP servers overview.