Skip to main content
Glama
samhavens

Databricks MCP Server

by samhavens

start_cluster

Activate a terminated Databricks cluster by specifying its unique cluster ID, enabling seamless resumption of data processing and analytics tasks.

Instructions

Start a terminated Databricks cluster

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
cluster_idYes

Implementation Reference

  • MCP tool handler for 'start_cluster': registers the tool using @mcp.tool() and implements the logic by calling the clusters API, handling errors, and returning JSON.
    @mcp.tool() async def start_cluster(cluster_id: str) -> str: """Start a terminated Databricks cluster""" logger.info(f"Starting cluster: {cluster_id}") try: result = await clusters.start_cluster(cluster_id) return json.dumps(result) except Exception as e: logger.error(f"Error starting cluster: {str(e)}") return json.dumps({"error": str(e)})
  • Core implementation of cluster start: makes POST request to Databricks Clusters API /api/2.0/clusters/start with cluster_id.
    async def start_cluster(cluster_id: str) -> Dict[str, Any]: """ Start a terminated Databricks cluster. Args: cluster_id: ID of the cluster to start Returns: Empty response on success Raises: DatabricksAPIError: If the API request fails """ logger.info(f"Starting cluster: {cluster_id}") return make_api_request("POST", "/api/2.0/clusters/start", data={"cluster_id": cluster_id})

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/samhavens/databricks-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server