Databricks MCP Server

### Related Issues/PRs <!-- Uncomment 'Resolve' if this PR can close the linked items. --> <!-- Resolve --> #xxx ### What changes are proposed in this pull request? <!-- Please fill in changes proposed in this PR. --> ### How is this PR tested? - [ ] Existing unit/integration tests - [ ] New unit/integration tests - [ ] Manual tests <!-- Attach code, screenshot, video used for manual testing here. --> ### Does this PR require documentation update? - [ ] No. You can skip the rest of this section. - [ ] Yes. I've updated the relevant server README.md ### Release Notes #### Is this a user-facing change? - [ ] No. You can skip the rest of this section. - [ ] Yes. Give a description of this change to be included in the release notes. <!-- Details in 1-2 sentences. You can just refer to another PR with a description if this PR is part of a larger change. --> <!-- Insert an empty named anchor here to allow jumping to this section with a fragment URL (e.g. https://github.com/mlflow/mlflow/pull/123#user-content-release-note-category). Note that GitHub prefixes anchor names in markdown with "user-content-". --> <a name="release-note-category"></a> #### 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" section - [ ] `rn/breaking-change` - The PR will be mentioned in the "Breaking Changes" section - [ ] `rn/feature` - A new user-facing feature worth mentioning in the release notes - [ ] `rn/bug-fix` - A user-facing bug fix worth mentioning in the release notes - [ ] `rn/documentation` - A user-facing documentation change worth mentioning in the release notes