Feature Request
GitMCP currently supports SSE transport only.
Please add STDIO transport as an alternative connection method.
Why
Many agent frameworks and CLI-based MCP orchestrators (e.g. mcp2cli)
operate primarily over STDIO. Having to handle SSE separately from
STDIO-based MCP servers adds unnecessary complexity for teams running
fully local or self-hosted agent pipelines.
Proposed Solution
Support STDIO as an optional transport alongside the existing SSE,
following the same pattern as other dual-transport MCP servers.
This would allow users to connect via:
npx gitmcp --stdio {owner}/{repo}or via a local wrapper that proxies STDIO to the existing SSE endpoint.
Impact
Would make GitMCP fully compatible with STDIO-first agent pipelines
without requiring any changes to existing SSE users.
Feature Request
GitMCP currently supports SSE transport only.
Please add STDIO transport as an alternative connection method.
Why
Many agent frameworks and CLI-based MCP orchestrators (e.g. mcp2cli)
operate primarily over STDIO. Having to handle SSE separately from
STDIO-based MCP servers adds unnecessary complexity for teams running
fully local or self-hosted agent pipelines.
Proposed Solution
Support STDIO as an optional transport alongside the existing SSE,
following the same pattern as other dual-transport MCP servers.
This would allow users to connect via:
npx gitmcp --stdio {owner}/{repo}or via a local wrapper that proxies STDIO to the existing SSE endpoint.
Impact
Would make GitMCP fully compatible with STDIO-first agent pipelines
without requiring any changes to existing SSE users.