Loading…
Bring Databricks into Kiro IDE with the AI Dev Kit Power
Antony Prasad Thevaraj, Venkatavaradhan Viswanathan
- Source
- Databricks
- Published
- Added to Yomu
Summary
AI-assisted development can produce unreliable SQL and models when an assistant guesses schema details or exceeds the user's data access. Kiro can connect to Databricks through Model Context Protocol (MCP) in two ways: four Databricks-managed remote servers for Genie, SQL, Unity Catalog Functions, and Vector Search, or the Databricks AI Dev Kit Power, which installs a local Python MCP server and broader skills. The AI Dev Kit now supports Kiro through its unified installer, while the Power provides one-click onboarding with authentication detection and skill loading. Both paths use Unity Catalog permissions, including row-, column-, and tag-based grants, so the assistant sees the user's effective access; Path A uses token-based configuration, while Path B supports OAuth U2M, OAuth M2M, profiles, or PATs. Examples show schema-grounded SQL, dbt joins using real columns, query comparisons, lineage checks, and generation of Databricks jobs or Asset Bundles.
Context
AI-assisted development becomes unreliable when the assistant has to guess column names, table layouts, schemas, or accessible catalogs. The integration is intended to ground Kiro in live Databricks workspace metadata while preserving the user's existing Unity Catalog permissions.
Approach / What changed
The post presents two integration paths: configure four Databricks-managed remote MCP servers for Genie, SQL, Unity Catalog Functions, and Vector Search, or install the Databricks AI Dev Kit Power for Kiro. The Power runs onboarding, authentication detection, MCP wiring, and skill loading, with support for OAuth U2M, OAuth M2M, .databrickscfg profiles, and PATs.
Takeaways
- The AI Dev Kit's unified installer treats Kiro as a first-class target and places skills in ~/.kiro/skills/ and MCP settings in ~/.kiro/settings/mcp.json.
- MCP initialization can succeed with a placeholder resource URL while later tool calls fail with RESOURCE_DOES_NOT_EXIST or PERMISSION_DENIED, so Genie spaces, Unity Catalog Functions, vector indexes, and permissions need pre-flight checks.
- Kiro must be fully quit and relaunched after environment-variable or authentication changes because it reads those variables at process start; reloading the window is insufficient.