Rename experimental/apps-mcp to experimental/aitools (#4220)

Renames the experimental/apps-mcp directory to experimental/aitools and
updates all references throughout the codebase.

Changes:
- Rename experimental/apps-mcp/ directory to experimental/aitools/
- Update all import paths from apps-mcp to aitools
- Rename CLI command from 'databricks experimental apps-mcp' to
'databricks experimental aitools'
- Update display names from 'Apps MCP'/'Databricks MCP' to 'Databricks
aitools'
- Rename MCP server name from 'databricks-apps-mcp' to
'databricks-aitools'
- Update config/history path from ~/.databricks/apps-mcp to
~/.databricks/aitools
- Update test targets from test-exp-apps-mcp to test-exp-aitools
- Update CODEOWNERS and GitHub Actions workflow references

All tests pass and the code builds successfully.

---------

Co-authored-by: Claude Sonnet 4.5 <noreply@anthropic.com>

Author: fjakobs

.github/CODEOWNERS

@@ -7,4 +7,4 @@
 /cmd/workspace/apps/      @databricks/eng-app-devex
 /libs/apps/               @databricks/eng-app-devex
 /acceptance/apps/         @databricks/eng-app-devex
-/experimental/apps-mcp/   @databricks/eng-app-devex @lennartkats-db
+/experimental/aitools/    @databricks/eng-app-devex @lennartkats-db

.github/workflows/push.yml

@@ -145,14 +145,14 @@ jobs:
       - name: Analyze slow tests
         run: make slowest
 
-  test-exp-apps-mcp:
+  test-exp-aitools:
     needs:
       - cleanups
       - testmask
 
     # Only run if the target is in the list of targets from testmask
-    if: ${{ contains(fromJSON(needs.testmask.outputs.targets), 'test-exp-apps-mcp') }}
-    name: "make test-exp-apps-mcp"
+    if: ${{ contains(fromJSON(needs.testmask.outputs.targets), 'test-exp-aitools') }}
+    name: "make test-exp-aitools"
     runs-on: ${{ matrix.os }}
 
     strategy:
@@ -171,11 +171,11 @@ jobs:
       - name: Setup build environment
         uses: ./.github/actions/setup-build-environment
         with:
-          cache-key: test-exp-apps-mcp
+          cache-key: test-exp-aitools
 
       - name: Run tests
         run: |
-          make test-exp-apps-mcp
+          make test-exp-aitools
 
   test-exp-ssh:
     needs:
@@ -251,7 +251,7 @@ jobs:
   test-result:
     needs:
       - test
-      - test-exp-apps-mcp
+      - test-exp-aitools
       - test-exp-ssh
       - test-pipelines
 

.gitignore

@@ -38,6 +38,9 @@ tools/yamlfmt.exe
 # Built by make for 'make lint'
 tools/golangci-lint
 
+# Built by make for test filtering
+tools/testmask/testmask
+
 # Cache for tools/gh_report.py
 .gh-logs
 

Makefile

@@ -173,8 +173,8 @@ generate:
 
 .PHONY: lint lintfull tidy lintcheck fmt fmtfull test test-unit test-acc test-slow test-slow-unit test-slow-acc cover showcover build snapshot snapshot-release schema integration integration-short acc-cover acc-showcover docs ws wsfix links checks test-update test-update-templates generate-out-test-toml test-update-aws test-update-all generate-validation
 
-test-exp-apps-mcp:
-	make test TEST_PACKAGES="./experimental/apps-mcp/..." ACCEPTANCE_TEST_FILTER="TestAccept/idontexistyet/apps-mcp"
+test-exp-aitools:
+	make test TEST_PACKAGES="./experimental/aitools/..." ACCEPTANCE_TEST_FILTER="TestAccept/idontexistyet/aitools"
 
 test-exp-ssh:
 	make test TEST_PACKAGES="./experimental/ssh/..." ACCEPTANCE_TEST_FILTER="TestAccept/ssh"

acceptance/apps/init-template/app/script

@@ -1,4 +1,4 @@
 #!/bin/bash
-$CLI experimental apps-mcp tools init-template app --name test_app --sql-warehouse-id abc123 --output-dir output > /dev/null 2>&1
+$CLI experimental aitools tools init-template app --name test_app --sql-warehouse-id abc123 --output-dir output > /dev/null 2>&1
 echo "✓ Template instantiation succeeded"
 rm -rf output

acceptance/apps/init-template/empty/script

@@ -1,4 +1,4 @@
 #!/bin/bash
-$CLI experimental apps-mcp tools init-template empty --name test_empty --catalog main --output-dir output > /dev/null 2>&1
+$CLI experimental aitools tools init-template empty --name test_empty --catalog main --output-dir output > /dev/null 2>&1
 echo "✓ Template instantiation succeeded"
 rm -rf output

acceptance/apps/init-template/job/script

@@ -1,4 +1,4 @@
 #!/bin/bash
-$CLI experimental apps-mcp tools init-template job --name test_job --catalog main --output-dir output > /dev/null 2>&1 || exit 1
+$CLI experimental aitools tools init-template job --name test_job --catalog main --output-dir output > /dev/null 2>&1 || exit 1
 echo "✓ Template instantiation succeeded"
 rm -rf output

acceptance/apps/init-template/pipeline/script

@@ -1,4 +1,4 @@
 #!/bin/bash
-$CLI experimental apps-mcp tools init-template pipeline --name test_pipeline --language python --catalog main --output-dir output > /dev/null 2>&1
+$CLI experimental aitools tools init-template pipeline --name test_pipeline --language python --catalog main --output-dir output > /dev/null 2>&1
 echo "✓ Template instantiation succeeded"
 rm -rf output

cmd/experimental/experimental.go

@@ -1,7 +1,7 @@
 package experimental
 
 import (
-	mcp "github.com/databricks/cli/experimental/apps-mcp/cmd"
+	mcp "github.com/databricks/cli/experimental/aitools/cmd"
 	"github.com/spf13/cobra"
 )
 

experimental/apps-mcp/README.md experimental/aitools/README.mdexperimental/apps-mcp/README.md renamed to experimental/aitools/README.md

@@ -1,4 +1,4 @@
-# Databricks MCP Server
+# Databricks AI Tools
 
 A Model Context Protocol (MCP) server for working with Databricks through natural language. This server provides tools for data exploration, workspace management, and executing Databricks CLI commands through AI-powered conversations.
 
@@ -17,19 +17,19 @@ A Model Context Protocol (MCP) server for working with Databricks through natura
 - **Conversational interface**: Work with Databricks using natural language instead of memorizing CLI commands
 - **Context-aware**: Get relevant command suggestions based on your workspace configuration
 - **Unified workflow**: Combine data exploration, bundle management, and app deployment in one tool
-- **Transparency**: Every MCP tool call displays clear, branded output so you always know when Databricks MCP is working
+- **Transparency**: Every MCP tool call displays clear, branded output so you always know when Databricks AI Tools are working
 
 Perfect for data engineers and developers who want to streamline their Databricks workflows with AI-powered assistance.
 
 **Visual Feedback:**
-When using Databricks MCP, you'll see distinctive branded headers in your chat:
+When using Databricks AI Tools, you'll see distinctive branded headers in your chat:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🚀 Databricks MCP: App scaffolded successfully
+🚀 Databricks AI Tools: App scaffolded successfully
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
-This makes it immediately clear you're using the Databricks MCP server, not just plain Claude or Cursor. If you don't see these headers, the MCP server isn't connected (see Troubleshooting below).
+This makes it immediately clear you're using the Databricks AI Tools MCP server, not just plain Claude or Cursor. If you don't see these headers, the MCP server isn't connected (see Troubleshooting below).
 
 ---
 
@@ -39,7 +39,7 @@ This makes it immediately clear you're using the Databricks MCP server, not just
 
 1. **Install the MCP server automatically:**
    ```bash
-   databricks experimental apps-mcp install
+   databricks experimental aitools install
    ```
 
    This interactive command will:
@@ -94,7 +94,7 @@ If you prefer to configure manually or the automatic installation doesn't work:
   "mcpServers": {
     "databricks": {
       "command": "databricks",
-      "args": ["experimental", "apps-mcp"],
+      "args": ["experimental", "aitools"],
       "env": {
         "DATABRICKS_HOST": "https://your-workspace.databricks.com",
         "DATABRICKS_TOKEN": "dapi...",
@@ -111,16 +111,16 @@ Then restart your MCP client for changes to take effect
 
 ### Troubleshooting
 
-#### 🚨 Not seeing Databricks MCP headers in your chat?
+#### 🚨 Not seeing Databricks AI Tools headers in your chat?
 
 If you ask about Databricks or apps but **don't see the distinctive headers** like:
 ```
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
-🚀 Databricks MCP: App scaffolded successfully
+🚀 Databricks aitools: App scaffolded successfully
 ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 ```
 
-**You're using plain Claude/Cursor, not the Databricks MCP server!** This means:
+**You're using plain Claude/Cursor, not the Databricks AI Tools MCP server!** This means:
 - ❌ No access to Databricks data or tools
 - ❌ Generic AI responses instead of actual app generation
 - ❌ No scaffolding, validation, or deployment capabilities
@@ -156,7 +156,7 @@ If the MCP server doesn't connect or shows errors:
 5. **Check Databricks CLI:** Verify the CLI is installed and accessible:
    ```bash
    databricks --version
-   databricks experimental apps-mcp --help
+   databricks experimental aitools --help
    ```
 
 6. **Test authentication:** Try listing catalogs to verify credentials work:
@@ -175,7 +175,7 @@ If issues persist, please report them at https://github.com/databricks/cli/issue
 
 ## Features
 
-The Databricks MCP server provides CLI-based tools for workspace interaction:
+The Databricks AI Tools provide CLI-based tools for workspace interaction:
 
 Execute Databricks CLI commands and explore workspace resources:
 
@@ -321,10 +321,10 @@ The `invoke_databricks_cli` tool:
 
 ```bash
 # Install MCP server in coding agents (Claude Code, Cursor, etc.)
-databricks experimental apps-mcp install
+databricks experimental aitools install
 
 # Start MCP server (default mode)
-databricks experimental apps-mcp
+databricks experimental aitools
 ```
 
 ### Environment Variables