-
Notifications
You must be signed in to change notification settings - Fork 42
Update custom server instructions to support deploying both via apps & bundles CLI #36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update custom server instructions to support deploying both via apps & bundles CLI #36
Conversation
Signed-off-by: Sid Murching <sid.murching@databricks.com>
Signed-off-by: Sid Murching <sid.murching@databricks.com>
| apps: | ||
| custom-mcp-server: | ||
| name: "custom-mcp-server" | ||
| name: "mcp-custom-server-bundles" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
To avoid conflict with the one deployed via apps CLI
Signed-off-by: Sid Murching <sid.murching@databricks.com>
Signed-off-by: Sid Murching <sid.murching@databricks.com>
|
|
||
| # note the order of mounting here, | ||
| # and don't change it unless you know what you're doing | ||
| app.mount("/api", mcp_app) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We have some upcoming product features that expect that the MCP server is hosted at /mcp instead of /api/mcp (and /mcp is also the default when using FastMCP), so updating to reflect that
| <pre class="bg-gray-900 p-3 rounded overflow-x-auto"> | ||
| <code class="language-python"> | ||
| from databricks.sdk import WorkspaceClient | ||
| from databricks_mcp import DatabricksOAuthClientProvider |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Using this new API to configure auth. We'll also recommend this in docs
Related Issues/PRs
#xxxWhat changes are proposed in this pull request?
See title
How is this PR tested?
Manually ran through both the apps CLI and bundles deployment flows
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