Stdio Proxy

What stdio-proxy MCP server does

The stdio-proxy MCP server is the client-facing bridge for Undisk MCP. It connects MCP clients that launch local processes over standard input and output with the hosted Undisk MCP API, which communicates over HTTP. The project is published as @undisk-mcp/stdio-proxy and is described as the stdio-to-HTTP bridge for Docker and local MCP clients.

This package belongs to the broader Undisk MCP system rather than providing a separate file-storage backend. Undisk places an MCP layer between an AI agent and the filesystem. Its storage model creates an immutable version for every write, audits actions, and supports reversing changes with a single call.

How it works

A compatible MCP client starts the stdio-proxy MCP server as a local process. The proxy translates the client’s stdio connection into requests to the hosted Undisk MCP service. This lets a client use a local-process configuration even when the underlying MCP endpoint is remote.

The repository does not contain the implementation. It is a public issue tracker for Undisk MCP and its related CLI, proxy package, and hosted API. For implementation details, service documentation, and account setup, use the Undisk documentation and support links rather than treating this repository as the server source.

The stdio-proxy MCP server is therefore most relevant when transport compatibility is the problem: the client supports stdio, while the MCP service is available through Undisk’s HTTP API. It is also relevant to deployments where the MCP client runs locally or inside Docker.

Setup and configuration

Install or obtain the proxy through the @undisk-mcp/stdio-proxy npm package. The README identifies the package but does not provide a complete launch command, configuration schema, environment-variable list, or client-specific configuration example. Those details should be taken from the package documentation or Undisk’s hosted documentation before deployment.

Undisk provides a signup page for obtaining an API key, and the README links to the hosted MCP API documentation. Because the proxy connects to that service, an operator should confirm the required credential and endpoint settings in the current documentation. No credential variable name can be established from the supplied material.

Tools and capabilities

The underlying Undisk MCP service advertises 25 MCP tools across these areas:

• File operations
• Version control
• Workspace administration
• Introspection
• Sandboxed compute

The supplied material does not enumerate individual tool names or define their parameters. The proxy’s documented role is transport bridging; it should not be assumed to add independent file, versioning, or compute operations beyond exposing the connected Undisk service to an MCP client.

Limitations and notes

The GitHub repository is an issue tracker, not the source distribution. It is intended for bug reports, feature requests, and questions concerning the CLI, stdio-proxy package, and hosted API. Before filing an issue, users are asked to search existing issues and include the CLI version or client information where relevant.

Undisk MCP is proprietary software. The tracker does not establish an open-source license for the proxy or the hosted service. Security vulnerabilities should be reported through the support email listed by the project rather than through public issues.