M1. stdio transport for the MCP server
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 55/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- csharp
- Domain
- api, cli, documentation
Research direction
Start by reading the MCP server behavior and CLI startup path, then review the proposed transport options in the issue. Use docs/mcp.md and the existing test layout to determine where transport selection is covered. Done means stdio works end-to-end, HTTP remains unchanged, transport selection is tested, and both transports are documented.
Written by the indexing model from the issue text.
Description
Why
MCP is HTTP-only today (default port 6128). The most common MCP client integration pattern (Claude Desktop, many IDE agents, sandboxed hosts) launches servers over stdio. HTTP-only is a hard compatibility wall and forces port management. With adoption growing across 60+ accounts, broadening client reach is the highest-leverage agent investment.
Proposed behavior
--mcp-stdio(or--mcp --transport stdio) starts the server on stdio; keep HTTP as an option.- Document both transports in
docs/mcp.md.
Acceptance criteria
- Server usable from a stdio MCP client end-to-end.
- HTTP behavior unchanged.
- Tests cover transport selection.
- Docs updated.
Filed from the Agentic & Automation Roadmap (docs/agentic-roadmap.md), item M1, Wave 1. Priority P0.
- Dominant language
- C#
- Stars
- 3
- Forks
- 7
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 18
Contributor guide
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.
More from Azure/CosmosDBShell
-
automation P1
Difficulty 5/5 Over a week Newbie friendliness 45/100
Azure/CosmosDBShell#178 · 1 comment ·
-
automation P1
Difficulty 5/5 Over a week Newbie friendliness 35/100
Azure/CosmosDBShell#175 · 1 comment ·
-
agentic enhancement P1
Difficulty 5/5 Over a week Newbie friendliness 35/100
Azure/CosmosDBShell#159 · 2 comments ·
-
Difficulty 5/5 Over a week Newbie friendliness 30/100
Azure/CosmosDBShell#118 · 1 comment ·
-
enhancement
Difficulty 5/5 Over a week Newbie friendliness 45/100
Azure/CosmosDBShell#107 · 3 comments ·
All issues in Azure/CosmosDBShell
Similar issues
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
nightscout/nocturne#1425 ·
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
Documentation
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
cake-build/cake#5024 ·
-
Frontend status/draft TechnicalDebt
Difficulty 2/5 1-2 days Newbie friendliness 75/100
Altinn/altinn-auth#4143 ·