[Positioning] PM Decision — Scope: DocumentDB-only vs. Mongo-compatible (incl. Atlas)?

Decision needed

Is this MCP server:

• (A) DocumentDB-only — primary target is Azure DocumentDB; other backends are unsupported / undocumented.
• (B) DocumentDB-first, Mongo-compatible best-effort — test against DocumentDB, don't gate Atlas usage, don't write Atlas-specific code, set expectations in docs.
• (C) Generic Mongo-compatible — Atlas first-class; compete directly with mongodb-mcp-server.

Why this matters

• Drives API choices (Mongo wire protocol vs. Data API, etc.).
• Drives OSS positioning and support commitment.
• Drives whether features that only exist in one backend are gated.
• Drives README messaging.

Recommendation

(B). Keeps the value prop sharp (Azure-native, Entra-integrated, security-first) without slamming the door on the curious Atlas user. Avoids competing head-on with mongodb-mcp-server without a clear differentiator.

Acceptance criteria

• Decision documented in this issue.
• README updated to match the chosen scope.
• Test matrix updated accordingly.

Blocks

Several DX issues depend on knowing the scope before writing docs.