Manage Databricks workspace connections: check current workspace, switch profiles, list available workspaces, or authenticate to a new workspace. Use when the user mentions "switch workspace", "which workspace", "current profile", "databrickscfg", "connect to workspace", or "databricks auth".
100
100%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Use the manage_workspace MCP tool for all workspace operations. Do NOT edit ~/.databrickscfg, use Bash, or use the Databricks CLI.
Call ToolSearch with query select:mcp__databricks__manage_workspace to load the tool.
Map user intent to action:
action="status"action="list"list first to find the profile name, then action="switch", profile="<name>" (or host="<url>" if a URL was given)action="login", host="<url>"Call mcp__databricks__manage_workspace with the action and any parameters.
Present the result. For status/switch/login: show host, profile, username. For list: formatted table with the active profile marked.
Note: The switch is session-scoped — it resets on MCP server restart. For permanent profile setup, use
databricks auth login -p <profile>and update~/.databrickscfgwithcluster_idorserverless_compute_id = auto.
b4071a0
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.