gcloud beta services mcp enable

gcloud beta services mcp enable - enable a service for MCP on a project, folder or organization

gcloud beta services mcp enable SERVICE [--async] [--skip-mcp-endpoint-check] [--folder=FOLDER_ID     | --organization=ORGANIZATION_ID     | --project=PROJECT_ID] [GCLOUD_WIDE_FLAG …]

gcloud beta services mcp enable my-service

To enable a service for MCP called my-service on the project my-project, run:

gcloud beta services mcp enable my-service --project=my-project

To enable a service for MCP called my-service on the folder my-folder, run:

gcloud beta services mcp enable my-service --folder=my-folder

To enable a service for MCP called my-service on the organization my-organization, run:

gcloud beta services mcp enable my-service --organization=my-organization

gcloud beta services mcp enable my-service --async

SERVICE

The name of the service to enable MCP.

--async

Return immediately, without waiting for the operation in progress to complete.

--skip-mcp-endpoint-check

If true, the system will bypass the check for MCP endpoint while enabling a service.

At most one of these can be specified:

--folder=FOLDER_ID

The Google Cloud Platform folder ID to use for this invocation.

--organization=ORGANIZATION_ID

The Google Cloud Platform organization ID to use for this invocation.

--project=PROJECT_ID

The Google Cloud project ID to use for this invocation. If omitted, then the current project is assumed; the current project can be listed using gcloud config list --format='text(core.project)' and can be set using gcloud config set project PROJECTID.

--project and its fallback core/project property play two roles in the invocation. It specifies the project of the resource to operate on. It also specifies the project for API enablement check, quota, and billing. To specify a different project for quota and billing, use --billing-project or billing/quota_project property.

Run $ gcloud help for details.