mcp-stdio-wrapper

[](https://github.com/JoshuaGreeff/mcp-stdio-wrapper/actions/workflows/ci.yml) [](https://github.com/JoshuaGreeff/mcp-stdio-wrapper/actions/workflows/codeql.yml) [](https://github.com/JoshuaGreeff/mcp-stdio-wrapper/actions/workflows/scorecard.yml) [](https://github.com/JoshuaGreeff/mcp-stdio-wrapper/actions/workflows/release.yml) [](./LICENSE) [](https://github.com/JoshuaGreeff/mcp-stdio-wrapper/stargazers)

MCP Stdio Wrapper is a small MCP server that lets one MCP client launch and inspect another stdio MCP server on demand.

Its job is to remove a painful MCP development loop: some mainstream MCP hosts cache the real server process, so after every code change you end up refreshing the window or restarting the extension host just to smoke-test the change. This wrapper sits in front of the real target server and gives your agent a stable bridge for repeated smoke tests while the target implementation keeps changing underneath it.

Use this project when:

• you are actively developing a stdio MCP server
• your main MCP host does not reliably reload the target server after each change
• you still want an agent to list tools, call tools, read resources, and inspect prompts throughout development

This project is intentionally narrow. It is for local develop