Hosting

Google-managed remote

Transport

Streamable HTTP

Endpoint

https://dataproc.googleapis.com/mcp

Authentication

Google Cloud authentication: OAuth 2.0 using Application Default Credentials (ADC) in supported Google clients, or a client OAuth ID/secret or bearer token in compatible third-party clients. The principal needs mcp.tools.call plus the underlying product permissions; API key authentication is only available for services that explicitly support it.

Requirements

• A Google Cloud project and access to the target product/resource.
• Enable this MCP service and its underlying Google Cloud API as required by the product guide.
• An MCP client that supports Streamable HTTP.
• An identity with the MCP Tool User role (roles/mcp.toolUser) or equivalent mcp.tools.call permission, plus permissions for the underlying product operations.

Setup steps

1. Choose the correct global or regional endpoint for your data location; this catalog lists the documented endpoint.
2. In the Google Cloud project, enable the MCP service and the underlying product API if the product guide requires it.
3. Authenticate the client with Google Cloud ADC (simplest with Antigravity/Gemini CLI) or configure OAuth 2.0 credentials in a compatible client.
4. Grant the connecting identity roles/mcp.toolUser and only the product IAM roles needed for the intended operations.
5. Add dataproc.googleapis.com to the client as a Streamable HTTP MCP server and complete sign-in.
6. Refresh the client tool list and check that the tools match the product reference; availability may depend on permissions and selected toolset.

Fifteen tools inspect/create/delete Dataproc clusters, jobs, batches and sessions. Provisioning may incur compute charges; delete tools can terminate workloads. Requires Dataproc IAM and service-account roles.

• list_clusters

  List Dataproc clusters in a Google Cloud project

  01
• get_cluster

  Get a Dataproc cluster in a Google Cloud project

  02
• create_cluster

  Create a Dataproc cluster in a Google Cloud project

  03
• delete_cluster

  Delete a Dataproc cluster in a Google Cloud project

  04
• list_jobs

  List Dataproc jobs in a Google Cloud project

  05
• get_job

  Get a Dataproc job in a Google Cloud project

  06
• list_batches

  List Dataproc batches in a Google Cloud project

  07
• get_batch

  Get a Dataproc batch in a Google Cloud project

  08
• create_batch

  Create a Dataproc Batch in a Google Cloud project

  09
• delete_batch

  Delete a Dataproc Batch in a Google Cloud project

  10
• list_sessions

  List Dataproc Sessions in a Google Cloud project

  11
• get_session

  Get a Dataproc session in a Google Cloud project

  12
• create_session

  Create a Dataproc Session in a Google Cloud project

  13
• delete_session

  Delete a Dataproc Session in a Google Cloud project

  14
• get_operation

  Gets the status of a long-running operation. Usage Some tools (for example, create_cluster and delete_cluster ) return a long-running operation. You can use this tool to get the status of the operation. It can be called repeatedly to poll the status of a long running operation Parameters * name : The name of the operation to get. * name should be the name returned by the tool that initiated the operation. * name should be in the format of projects/{project}/locations/{location}/operations/{operation} .

  15

• official tool reference

  Product-specific Google MCP reference publishes 15 exact tool identifiers and descriptions in its tools reference.

• official server catalog

  Official Google Cloud catalog lists this product as an available remote MCP server.

• official setup guide

  Google Cloud describes remote MCP client setup, Streamable HTTP transport, supported authentication options, and ADC setup.

• official authentication guide

  Google documents supported identity types and authorization requirements for Google Cloud MCP calls.

• official source

  Official Google Cloud primary MCP reference/setup checked 2026-10-28.

• official source

  Official Google Cloud primary MCP reference/setup checked 2026-10-28.

Documentation checked 2026-10-28. Connection has not been runtime tested.