GitHub Repository

Config-driven MCP proxy that adds session-safe file uploads, artifact handling, and robust state and health controls for upstream MCP servers. Also provides code-mode for servers that don't yet support it.

3 starsPython

Making remote MCP servers handle local files and generated artifacts

Name: Making remote MCP servers handle local files and generated artifacts
Availability: InStock
Author: aakashh242

by aakashh242·Mar 6, 2026·1 point·0 comments

Visit Project View on HN

AI Analysis

●●SolidSolve My ProblemNiche Gem

Remote MCP file bridge with sessions and artifact capture, but niche until MCP adoption broadens.

Strengths

•Session-scoped file isolation and TTL cleanup prevent artifact leakage in multi-client setups.
•Unified artifact reference model (artifact://) lets tools write; client retrieves without FTP.
•State backend flexibility (in-memory, SQLite, Redis) scales from dev to multi-node.

Weaknesses

•MCP spec and ecosystem still young; tool compatibility and upstream stability unproven.
•Requires deep MCP knowledge to deploy; documentation light on production gotchas.

Post Description

Most MCP examples look clean when the client and server run on the same machine.

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.