[WIP] Prototype/POC of remote server support + hosting on Databricks apps #22
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.
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
Just snapshotting / pushing some POC work towards enabling hosting the UC MCP server on Databricks apps. To get things to work, I:
USE CATALOG
,USE SCHEMA
,Query
on Genie spaces,SELECT
on VS indexes, etc) on the necessary resourcesdatabricks auth login --profile <your-profile-here>
and then running the following scriptAuthorization
header in MCP inspectorI'm seeing some occasional server disconnects etc but I hope that'll go away once we can switch to streamable HTTP transport & clients support it. It seems client support is coming soon, with the first step of server support in modelcontextprotocol/python-sdk#553
How is this PR tested?
Does this PR require documentation update?
Release Notes
Is this a user-facing change?
How should the PR be classified in the release notes? Choose one:
rn/none
- No description will be included. The PR will be mentioned only by the PR number in the "Small Bugfixes and Documentation Updates" sectionrn/breaking-change
- The PR will be mentioned in the "Breaking Changes" sectionrn/feature
- A new user-facing feature worth mentioning in the release notesrn/bug-fix
- A user-facing bug fix worth mentioning in the release notesrn/documentation
- A user-facing documentation change worth mentioning in the release notes