Skip to content

docs: add release & distribution one-pager for managed MCP server#90

Open
hossain-rayhan wants to merge 2 commits into
microsoft:mainfrom
hossain-rayhan:rayhan/release-and-distribution
Open

docs: add release & distribution one-pager for managed MCP server#90
hossain-rayhan wants to merge 2 commits into
microsoft:mainfrom
hossain-rayhan:rayhan/release-and-distribution

Conversation

@hossain-rayhan

Copy link
Copy Markdown
Collaborator

Adds a one-pager that proposes how to release the DocumentDB MCP Server to customers at scale covering self-host, managed per-cluster, and shared multi-tenant pool topologies, plus the full list of distribution channels (Anthropic MCP Registry, VS Code / Copilot Gallery, OpenAI MCP connectors, Cursor, Azure Marketplace, MCR, npm, etc.).

Signed-off-by: Rayhan Hossain <hossain.rayhan@outlook.com>
@lionelc

lionelc commented Jun 5, 2026

Copy link
Copy Markdown
Collaborator

@khelanmodi The distribution plan is a big jump to managed server, which means a completely overhaul on business model (if compared to CosmosDB). Could you please do some market research to justify ROI?

  1. Any database company has an existing product with the standalone managed MCP server which charges separately instead of a bundle.
  2. For companies that do have MCPaaS or the likes, what capabilities do they provide in their service? What is their potential moat?
  3. If we are to go with the MCPaaS route, what would be our differentiator that can win the potential competition?

Since it's on business model, I believe the above questions will surely be asked when this plan is brought up. However, I don't see any mention on the competitive landscape or ROI analysis.

Signed-off-by: Rayhan Hossain <hossain.rayhan@outlook.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants