Databricks Platform
Wire Claude Code into Databricks for Delta Lake pipelines, MLOps jobs, and Unity Catalog governance without re-learning the workspace APIs each sprint.
Overview
databricks-platform is a plugin marketplace for the Build phase that connects Claude Code to Databricks engineering, MLOps, and governance workflows across three coordinated plugins.
What is this marketplace?
- 3 plugins: databricks-engineering (required), databricks-mlops, databricks-governance
- Covers PySpark pipeline automation, Delta Lake, Unity Catalog, and Delta Sharing workflows
- Featured engineering and MLOps plugins for featured discovery in Claude marketplace
- Free marketplace model with commercial license and GitHub Discussions enterprise support
- Metadata tags span data-quality, pipeline-automation, and data-products patterns
- 3 plugins in the marketplace
- 1 required plugin: databricks-engineering
- 2 featured plugins: databricks-engineering and databricks-mlops
Community signal: 4 GitHub stars.
What problem does it solve?
Agent-assisted coding stalls when lakehouse pipelines, catalog rules, and ML job setup live outside Claude and force constant notebook context-switching.
Who is it for?
Indie builders and small data teams already on Databricks who want agent-native Delta, Spark, and Unity Catalog tasks in the same repo as application code.
Skip if: Greenfield apps with no warehouse dependency, or teams that only need a one-off SQL snippet without ongoing pipeline or catalog work.
What do I get? / Deliverables
After you register the marketplace and enable databricks-engineering, Claude can drive Databricks-oriented implementation with optional MLOps and governance plugins as you ship and operate.
- Registered marketplace with three installable Databricks plugins
- Required databricks-engineering capability for agent-driven lakehouse tasks
- Optional MLOps and governance plugin surfaces for later journey phases
Plugins in this marketplace
3 plugins — install individually after you add the marketplace.
Recommended Marketplaces
Journey fit
Solo builders usually add this marketplace when the product needs a governed lakehouse integration during implementation, before day-two ops work. Databricks-engineering maps to external data-platform hooks—jobs, Spark, Delta—that belong on the integrations shelf rather than generic backend CRUD.
How it compares
Curated Databricks plugin bundle, not a single generic DevOps skill or a standalone MCP server listing.
Common Questions / FAQ
Who is Databricks Platform for?
It is for solo builders and small teams shipping on Databricks who want Claude Code plugins for engineering, and optionally MLOps and governance, instead of ad-hoc notebook prompts.
When should I use Databricks Platform?
Use it when you are implementing lakehouse integrations, automated pipelines, or catalog-backed data products and need those flows available inside your agent workspace.
How do I add Databricks Platform to my agent?
Add the vivekgana/Databricks Platform-marketplace repository as a Claude Code plugin marketplace, then install the required databricks-engineering plugin before enabling mlops or governance.