microsoft / microsoft/documentdb-mcp
[Positioning] PM Decision — Primary audience persona
Open
@khelanmodi is already working on this.
Since May 13, 2026.
decision
positioning
tier-1
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 3
Description
Decision needed
Who is the primary user of this MCP server?
Candidates:
- (A) Developers building AI agents/apps on Azure DocumentDB.
- (B) Data engineers / ops doing AI-assisted data exploration.
- (C) DBAs doing routine ops.
- (D) Any DocumentDB user.
Why this matters
Without a named primary persona (and named non-audiences), every feature request gets weighed against five competing users and nothing ships.
Recommendation
(A) primary, (B) secondary. Not (C), not (D).
- (C) is better served by Compass, mongosh, the Azure portal.
- (D) is too broad — every feature is a trade-off; we need to know whose trade-off we're optimizing.
Acceptance criteria
- Personas documented in
docs/audiences.mdor README. - Decision used to triage feature requests going forward.
- Comparison page references the chosen audience.
Blocks
Several positioning artifacts (comparison table, Use this when section, personas page).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.