That breaks once the MCP server is remote. Tools that expect local files cannot access them, and tools that generate files leave those artifacts stranded on the server.
I built remote-mcp-adapter to bridge that gap. It stages client-side files for upstream tools, captures output artifacts, and keeps normal MCP traffic flowing through unchanged.
Repo: https://github.com/aakashh242/remote-mcp-adapter
Would love feedback from people building remote or centralized MCP setups.