Stdio Proxy
Give coding agents durable, safer file memory through Undisk instead of stuffing huge paths and blobs into every chat turn.
Overview
app.undisk.mcp/stdio-proxy is an MCP server for the Build phase that provides Undisk safe file memory for AI coding agents over stdio.
What is this MCP server?
- Undisk-backed file memory exposed over MCP stdio
- Designed as safer disk access for agent workflows
- npm @undisk-mcp/stdio-proxy registry v0.46.2
- Requires UNDISK_API_KEY from mcp.undisk.app docs
- GitHub repo undisk-mcp-tracker for setup reference
- Registry version 0.46.2
- npm identifier @undisk-mcp/stdio-proxy
- Required env UNDISK_API_KEY
Community signal: 1 GitHub stars.
What problem does it solve?
Agents lose context across long builds or dump sensitive files into chat because there is no controlled file memory layer.
Who is it for?
Builders running multi-step agent workflows who want hosted file memory with API-key gating instead of wide-open local disk tools.
Skip if: Teams that forbid cloud file services, need only ephemeral in-repo edits, or want a self-hosted memory server with no Undisk account.
What do I get? / Deliverables
Your agent reads and writes through Undisk’s MCP proxy so file memory stays structured, keyed, and outside bloated prompts.
- MCP-accessible Undisk file memory for agent sessions
- Reduced reliance on pasting large files into prompts
- Clearer separation between chat context and on-disk agent artifacts
Recommended MCP Servers
Journey fit
Build is where you wire agent tooling; persistent file memory supports implementation and long-running agent sessions. Agent-tooling is the right shelf for MCP infrastructure that extends what agents can remember and touch on disk.
How it compares
Hosted safe file-memory MCP—not a vector RAG database or a generic filesystem skill.
Common Questions / FAQ
Who is app.undisk.mcp/stdio-proxy for?
Solo developers and agent power users who want Undisk-managed file memory available from Claude Code, Cursor, or other stdio MCP clients.
When should I use app.undisk.mcp/stdio-proxy?
Use it during Build agent-tooling setup when sessions need persistent artifacts, scratch storage, or safer disk operations across multiple agent turns.
How do I add app.undisk.mcp/stdio-proxy to my agent?
Obtain UNDISK_API_KEY per https://mcp.undisk.app/docs, install @undisk-mcp/stdio-proxy from npm, add the stdio server and secret to your MCP config, then reconnect your agent.