[Daniel G. Epstein (dgepstein)]

NOT READY FOR MERGE

Draft for inspection and discussion only. Do not mark ready, enable auto-merge, or merge this PR, including an administrator merge. A separate readiness decision is required after the outstanding checks below. The title warning communicates intent; draft status must be preserved.

Related backlog story: #269. Keep that issue open.

Summary

Split the existing Azure Databricks Foundry catalog entry into distinct Genie Agent and Genie One connectors:

• Replace partners/servers/azure-databricks-mcp-server.json with partners/servers/azure-databricks-genieagent-mcp-server.json, retaining /api/2.0/mcp/genie/{genie_space_id}.
• Add partners/servers/azure-databricks-genieone-mcp-server.json using the explicitly requested non-Unity endpoint /api/2.0/mcp/genie.
• Use new distinct catalog names, OAuth keys, and assumed connectorName registrations for both entries.
• Declare streamable HTTP and Entra v2 HTTPS authorization/token/refresh metadata; replace the mixed delegated-plus-.default scope configuration with the Databricks delegated permission and offline_access.
• Preserve legal, support, icon, vendor, visibility, and version metadata; retain preview markers and update descriptions/documentation.

Lifecycle limitation: the chosen non-Unity Genie One beta endpoint is deprecated and scheduled to retire on November 30, 2026, per the current Microsoft Learn retirement notice. The user explicitly selected it after the retirement notice was raised. Both its summary and description disclose this. This PR does not implement Unity Gateway.

Outstanding Readiness Gates

• Confirm/provision the assumed managed registrations foundrydatabricksgenieagentmcp and foundrydatabricksgenieonemcp; their presence in JSON does not create a backend registration.
• Validate actual Foundry/Databricks consent, token audience/scopes, effective identity, endpoint/audience policy, transport, tools, data access, and refresh. No live integration test has run; cross-tenant support is not established.
• Resolve the operational disposition of the retiring Genie One endpoint before considering merge readiness.
• Review the downstream migration impact of removing the old catalog name and connector binding.
• Review hosted CI and maintainer feedback, then obtain an explicit human decision before changing this PR out of draft.

Validation Completed

• Full catalog schema validation passed for all 115 partner manifests using check-jsonschema 0.38.2 through python -m check_jsonschema.
• Optional URI-format support was enabled in an isolated validation environment; the full catalog passed, and an intentionally invalid icon URI was correctly rejected.
• Verified 115 unique server names, 123 unique security-scheme keys, no duplicate JSON properties, exact endpoint/identifier/OAuth requirements, length limits, and retirement disclosure.
• Reviewed the complete three-path diff; whitespace checks pass and community/registry/servers.json is unchanged.
• Repeated full schema validation on the committed content before publication. Local Python was 3.14.7; the repository workflow uses 3.12. Local results are not a claim that hosted CI passed.
• The terminology correction also passed full catalog schema validation with PowerShell Test-Json using the local schema references, duplicate-property/name/security-key checks, exact-change preservation checks, and whitespace checks; no dependency installation was needed.
• The retirement-date correction passed the changed manifest's schema validation, exact date-only change checks, and whitespace checks; the legacy endpoint remains unchanged.
• Hosted validation: validator run reports action_required with zero jobs executed. Maintainer action is outstanding; this is not a CI pass.

Scope Exclusions

No Unity Gateway implementation, community-registry change, schema/workflow/dependency change, cloud provisioning, credential/permission change, or claim of production readiness.

Published Branch

• Feature branch in dgepstein/MCP
• Head commit: 66b7f15c11f1790030854f4b84b06f64593e5324.
• The fork branch contains the original connector split, a follow-up terminology correction, and the retirement-date correction; the verified comparison contains only the two new manifests and removal of the original.
• origin remains Azure/MCP. The local feature branch tracks the additional fork remote; direct writes to origin remain unavailable.

Public References

• Genie One MCP and legacy beta retirement
• Per-agent Genie Agent MCP
• Azure Databricks Entra tokens and delegated permission
• Entra scopes and .default restrictions

[Daniel G. Epstein (dgepstein)]

Need to replace references to "Genie spaces" with "Genie agents".

[Daniel G. Epstein (dgepstein)]

For the Foundry PM reviewer: can you confirm that the exact managed connector registrations foundrydatabricksgenieagentmcp and foundrydatabricksgenieonemcp exist, or arrange provisioning before this PR is considered ready? Please confirm their intended endpoint and authentication bindings: Genie Agent to /api/2.0/mcp/genie/{genie_space_id} and Genie One to the legacy /api/2.0/mcp/genie endpoint, with the Entra user OAuth configuration declared in each manifest. These names are proposed registrations; adding them to the catalog does not provision them.

[Daniel G. Epstein (dgepstein)]

For the Foundry PM reviewer: is replacing the existing azure-databricks catalog identity and foundrydatabricksmcp connector binding with azure-databricks-genieagent / foundrydatabricksgenieagentmcp and azure-databricks-genieone / foundrydatabricksgenieonemcp the intended compatibility behavior? Please confirm the migration plan for existing consumers and saved connections, including whether the existing identity or binding must be preserved rather than removed. This is a request for the intended identity/migration contract, not a claim that the proposed split is invalid.