microsoft / microsoft/documentdb-mcp
[DX] Investigate hosted ephemeral sandbox
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 4
- Avg merge
- 6d 21h
- Merged PRs (30d)
- 3
Description
Goal
Remove install Docker first from the funnel.
What to ship
A spike investigating a Microsoft-hosted ephemeral sandbox that:
- Spins up a clean DocumentDB instance per user, pre-seeded with sample data.
- Exposes an MCP endpoint the user can hit from VS Code with a one-time token.
- Self-destructs after 1 hour.
Acceptance criteria
- Document the cost, security, and abuse-prevention model.
- Decide go / no-go before any engineering work.
- If go: prototype on Container Apps / ACI.
Why
Reduces first-success time from ~15 minutes to ~30 seconds for the curious user. High UX value but real operational cost — needs evaluation before commitment.
Depends on
- Positioning Q2 (self-hosted-only vs hosted runtime) — this is a wedge into the hosted-runtime question.
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.
Research direction
Start by assessing the Microsoft-hosted ephemeral sandbox described in the issue, including a per-user DocumentDB instance, MCP endpoint, one-time token, and one-hour lifetime. Compare Container Apps and ACI, then document the cost, security, and abuse-prevention model; done means a clear go/no-go decision before engineering work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100