[apps-mcp] Fix token-based authentication for default profile #4195
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
🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude Sonnet 4.5 <[email protected]>
lennartkats-db
temporarily deployed
to
test-trigger-is
GitHub Actions
Inactive
Collaborator
|
Commit: 4df311d
19 interesting tests: 14 KNOWN, 4 RECOVERED, 1 SKIP
Top 33 slowest tests (at least 2 minutes):
|
fjakobs
approved these changes
Jan 5, 2026
Collaborator
|
Commit: 56fc0db
26 interesting tests: 14 KNOWN, 5 flaky, 4 RECOVERED, 2 FAIL, 1 SKIP
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.
[apps-mcp] Fix token-based authentication for default profile
Changes
Fix authentication in
apps-mcpfor theDEFAULTprofile.Why
When
InvokeDatabricksCLIruns a subprocess, it setsDATABRICKS_HOSTexplicitly. This prevents the SDK from falling back to the DEFAULT profile in~/.databrickscfg, causing auth failures.The old code tried to pass
DATABRICKS_CONFIG_PROFILE, butGetDatabricksProfile()always returned empty because the profile was never stored in the session during auto-authentication.Passing the token directly works for all auth methods (OAuth, PAT, profile-based).
Tests
Manual testing via MCP server:
Root cause confirmed by reproducing SDK behavior directly:
OAuth-based auth also works since
Config.Tokenis populated with the OAuth access token after authentication.