Transfer ownership: microsoft/documentdb-mcp -> Azure/documentdb-mcp

Transfer ownership: microsoft/documentdb-mcp → Azure/documentdb-mcp

Why

The MCP server is the runtime piece of Azure DocumentDB's plugin distribution; its sibling repo Azure/documentdb-agent-kit is already under the Azure/ org. Conventionally, anything branded "Azure DocumentDB" lives under github.com/Azure for discoverability and consistency with the rest of the Azure SDK / CLI / template ecosystem.

Not urgent

GitHub redirects all old URLs indefinitely after a transfer, including npx github:microsoft/documentdb-mcp specs that customers may have saved. So this transfer can happen after v2 ships with no customer-visible breakage.

Tasks

• Confirm Azure/ org admins are willing to take the repo (it brings security advisories, secret-scanning quota, etc.)
• Confirm CODEOWNERS / team membership will translate cleanly (Azure org has different teams than microsoft org)
• Schedule transfer during a quiet window (no in-flight PRs that span repos)
• Execute: Settings → Danger Zone → Transfer ownership → Azure
• Verify redirects: git clone https://github.com/microsoft/documentdb-mcp.git should still work post-transfer
• Update all hardcoded microsoft/documentdb-mcp references in Azure/documentdb-agent-kit to Azure/documentdb-mcp (cosmetic — old refs still work via redirect, but new docs should use the new path)
• Update package.json repository and homepage fields
• Update README badges
• Re-publish next npm version under the new repo (provenance ties package to repo URL)

What does NOT change

• npx github:microsoft/documentdb-mcp continues to work indefinitely via GitHub's redirect
• Existing @azure/documentdb-mcp-server npm installs continue to work
• Issue / PR history transfers with the repo
• Stars, watchers, forks all carry over

Done when

• Repo lives at github.com/Azure/documentdb-mcp
• All in-org docs reference the new path
• Next npm release uses the new repo URL for provenance

Start with the repository transfer checklist in the issue, then inspect Azure/documentdb-agent-kit references, package.json, and README badges for the old repository path. Coordinate the Azure organization checks and transfer, update the listed references, and verify redirects and the next npm release use the new repository URL.