Thank you for adding support for Model Context Protocol (MCP) – this opens up valuable extensibility options.

Currently, it appears that MCP integration only supports remote (network-based) endpoints. I would like to request adding support for the stdio transport method, as defined by the MCP specification.

Use case:

I am working on extending mycoder to support GitLab, similarly to how GitHub is already integrated. There are already existing MCP-compatible agents that expose GitLab context via stdio (e.g. local daemons, shell-based MCP agents, or language-specific tooling), and being able to leverage them would significantly reduce the implementation complexity.

By supporting MCP over stdio, it becomes feasible to plug in a wide range of existing, local tooling with minimal friction.

Proposed benefit:

• Enables integration with local MCP agents without requiring network setup
• Unlocks GitLab support via existing stdio-based MCP tooling
• Better alignment with the flexibility intended by the MCP spec
• Encourages broader adoption of mycoder in environments with strict security policies

Let me know if you're open to this addition — I’d be happy to contribute or help test.

Related Issues

#240