Skip to content

Commit f1f58b1

Browse files
Updating readme with information about managed databricks mcp servers (#41)
* Updating readme with information about managed databricks mcp servers * Apply suggestions from code review Co-authored-by: Siddharth Murching <smurching@gmail.com> * Update README.md --------- Co-authored-by: Siddharth Murching <smurching@gmail.com>
1 parent 90c6677 commit f1f58b1

File tree

1 file changed

+9
-5
lines changed

1 file changed

+9
-5
lines changed

README.md

Lines changed: 9 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -9,6 +9,7 @@ Table of Contents
99
- [Table of Contents](#table-of-contents)
1010
- [Overview](#overview)
1111
- [Unity Catalog Server](#unity-catalog-server)
12+
- [Databricks Managed MCP servers](#databricks-managed-mcp-servers)
1213
- [Overview](#overview-1)
1314
- [Usage (locally via `stdio` transport)](#usage-locally-via-stdio-transport)
1415
- [Supported tools](#supported-tools)
@@ -21,13 +22,16 @@ Table of Contents
2122
- [Support](#support)
2223
- [Contributing](#contributing)
2324

25+
## Databricks Managed MCP servers
26+
Databricks provides ready-to-use MCP servers that let agents query data and access tools in Unity Catalog. Permissions are always enforced, so agents and users can only access the tools and data they’re allowed to. For more info see the Databricks docs [AWS](https://docs.databricks.com/aws/en/generative-ai/agent-framework/mcp#managed-mcp-servers)|[Azure](https://docs.databricks.com/gcp/en/generative-ai/agent-framework/mcp#compute-pricing)|[GCP](https://docs.databricks.com/gcp/en/generative-ai/agent-framework/mcp#managed-mcp-servers).
27+
2428
## Overview
2529
An experimental collection of [MCP](https://modelcontextprotocol.io/introduction) servers to help AI agents fetch enterprise data from Databricks, automate common developer actions on Databricks, etc:
2630

27-
* ![status: Beta](https://img.shields.io/badge/status-Beta-yellow?style=flat-square&logo=databricks)
28-
[Databricks Unity Catalog server](#unity-catalog-server): Fetch data and run tools registered in from Unity Catalog, making agents aware of your enterprise data
31+
* ![status: Deprecated](https://img.shields.io/badge/status-Beta-yellow?style=flat-square&logo=databricks)
32+
[Databricks Unity Catalog server](#unity-catalog-server): Fetch data and run tools registered in from Unity Catalog, making agents aware of your enterprise data. Note: this server is deprecated; Databricks recomemnds using [Managed MCP servers](#databricks-managed-mcp-servers) instead
2933
* ![status: Under construction](https://img.shields.io/badge/status-Under_construction-red?style=flat-square&logo=databricks)
30-
[Databricks developer tools server](#developer-tools-server): Perform common developer actions in Databricks, like creating and updating notebooks, running jobs, etc. This server is not yet usable, but contributions are welcome!
34+
[Databricks developer tools server](#developer-tools-server): Perform common developer actions in Databricks, like creating and updating notebooks, running jobs, etc. This server is not yet usable, but contributions are welcome!
3135
Note: if developing from within the Databricks product (e.g. using Databricks notebooks), we recommend using [Databricks Assistant](https://docs.databricks.com/aws/en/notebooks/databricks-assistant-faq)
3236

3337
The set of servers and tools in this repo is fluid and will evolve over time. We welcome contributions to this repo - please first
@@ -126,7 +130,7 @@ databricks auth token -p your-profile-name
126130

127131
If you are a developer iterating on the server implementation, you can repeat steps #2 and #3 to push your latest modifications to the server to your Databricks app.
128132

129-
Please note that both variables should be provided in both `deploy` and `run` commands. The `schema_full_name` variable is used to determine the schema to use for the server, while the `genie_space_ids` variable is used to determine which Genie spaces to use.
133+
Please note that both variables should be provided in both `deploy` and `run` commands. The `schema_full_name` variable is used to determine the schema to use for the server, while the `genie_space_ids` variable is used to determine which Genie spaces to use.
130134

131135
#### Using `databricks apps` CLI
132136

@@ -188,6 +192,6 @@ Any issues discovered through the use of this project should be filed as GitHub
188192

189193
## Contributing
190194

191-
We welcome contributions :) - see [CONTRIBUTING.md](./CONTRIBUTING.md) for details. Please make sure to read this guide before
195+
We welcome contributions :) - see [CONTRIBUTING.md](./CONTRIBUTING.md) for details. Please make sure to read this guide before
192196
submitting pull requests, to ensure your contribution has the best chance of being accepted.
193197

0 commit comments

Comments
 (0)