Improve apps-mcp visibility with branded output headers #4032
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Clarify that install command handles credentials automatically - Add explicit MCP client restart step - Add connection verification step with clear instructions - Expand troubleshooting section with 7 concrete steps: - Check MCP server status - Verify credentials - Check configuration file - Restart MCP client - Check Databricks CLI installation - Test authentication - Ask Claude for help These improvements provide users with a clearer setup flow and actionable troubleshooting steps instead of the previous brief message. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
This change makes it immediately clear to users when they're using the Databricks MCP server versus plain Claude/Cursor by adding distinctive branded headers to all MCP tool outputs. Changes: - Add branded headers to all MCP tool outputs (scaffold, validate, deploy) - Use user-friendly messages like "App scaffolded successfully" instead of technical tool names - Add visual feedback section to README explaining the branded headers - Add troubleshooting section for when MCP headers are not visible - Include example output showing the branded headers in action Output format example: ``` ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 🚀 Databricks MCP: App scaffolded successfully ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ ✅ Created appkit application at /path/to/app ``` This ensures users always know when Databricks MCP is working and helps them quickly identify when the MCP server is not connected. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
keugenek
requested review from
a team,
lennartkats-db and
pietern
as code owners
arsenyinfo
approved these changes
Nov 28, 2025
Integrates latest changes from main including MCP provider refactoring from deployment/io providers to clitools. Combined README improvements from both branches to maintain branded output messaging while incorporating CLI-focused workflow documentation.
keugenek
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
Collaborator
|
Commit: 739ed4e
24 failing tests:
Top 50 slowest tests (at least 2 minutes):
|
keugenek
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
keugenek
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
Explicitly ignore filepath.Walk error return value when counting files for success message. The file count is for display purposes only and walk errors don't affect template initialization success. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
keugenek
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
keugenek
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
Collaborator
|
Commit: eb890d2
18 failing tests:
Top 50 slowest tests (at least 2 minutes):
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR improves the Databricks MCP server user experience by adding distinctive branded headers to all tool outputs, making it immediately clear when users are working with the MCP server versus plain Claude/Cursor.
Changes
1. Branded Output Headers
Added clear, user-friendly headers to all MCP tool outputs:
🚀 Databricks MCP: App scaffolded successfully🔍 Databricks MCP: Validating your app🚢 Databricks MCP: Deploying to production2. README Improvements
3. User-Friendly Messages
Changed from technical tool names to friendly descriptions that users can understand
Example Output
Testing
Impact
Users will now immediately see when they're using the Databricks MCP server through distinctive branded headers. This helps with: