MCP Marketplace Validation
This page outlines the process for validating and publishing a Partner MCP Server to the Databricks Marketplace.
Prerequisites
Before starting MCP Marketplace validation:
- You must be a Databricks Data Partner. If you're not yet a partner, apply through the Partner Portal first.
- Have an MCP server ready with HTTP/OAuth authentication
Validation process
The process consists of three steps:
- Technical Validation
- Marketplace Onboarding
- Testing the Marketplace Listing
Step 1: Technical validation
Technical validation confirms that the MCP server integrates correctly with Databricks and supports end-to-end tool execution through Databricks-hosted LLMs.
Validation options
- Live validation during the Integration Review Call — Partners should perform validation directly in their own Databricks workspace when working with sensitive or customer data.
- Validation in a Databricks-owned Workspace — If a test MCP server with dummy data is available and authentication details are shared, a Partner Engineer can perform validation in a Databricks-managed workspace.
Partners should review the public MCP Server documentation before starting.
Details required
- MCP server URL (base endpoint)
- Access token or OAuth credentials (required for HTTP authentication)
Validation steps
- Create an External MCP Connection in Databricks using the provided MCP server URL and authentication details.
- Attach the MCP Connection to an LLM in Databricks Playground.
- Run an end-to-end test to verify MCP tool invocation and responses.
- If successful, the Partner Engineer marks the MCP integration as validated.
Required information for validation
As part of technical validation (and to prepare for Marketplace onboarding), Partners must provide the following:
| Item | Description |
|---|---|
| Short description | A brief overview of what the MCP server does and the problems it helps customers solve |
| Tools exposed | A list of tools currently available through the MCP server, with short descriptions. Include tools planned on the roadmap |
| Joint value proposition | Describe how joint customers will use the MCP integration with Databricks, including key use cases and the value unlocked by combining the Partner MCP server with Databricks capabilities |
Step 2: Marketplace onboarding
Once technical validation is complete, Partners must onboard their MCP server to the Databricks Marketplace.
The onboarding process covers:
- Applying to be a Marketplace Data Partner
- Creating a Provider Profile
- Creating an MCP Marketplace listing
- Requesting ISV Partner Manager/Partner Engineer approval for workspace allowlisting
- Publishing the listing
To authorize a workspace to create and manage MCP Marketplace listings, partners must provide their Databricks Account ID and Workspace ID.
Step 3: Testing the Marketplace listing
Partners test the MCP Marketplace listing end-to-end before publishing to ensure installation, authentication, and MCP tool invocation work as expected.
Testing steps:
- Install the MCP listing in a test workspace
- Configure authentication and connection details
- Attach the MCP server to a Databricks-hosted LLM
- Run a sample prompt to validate tool invocation
Once testing is complete and successful, the listing can proceed to final review and publication.
What's next
- Review the MCP Server documentation for technical details
- See Listings for Marketplace listing best practices
- Contact the Databricks Partner Engineering team through the Partner Portal for assistance