Session-safe uploads and artifacts for remote MCP servers

Name: Session-safe uploads and artifacts for remote MCP servers
Availability: InStock
Author: aakashh242

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

Visit Project View on HN

AI Analysis

●●SolidSolve My ProblemShip It

Fills a real gap in remote MCP workflows, but solves a niche infrastructure problem for early adopters.

Strengths

•Thoughtful session isolation, TTL cleanup, quotas, and health checks — production infrastructure thinking for a proxy.
•upload:// and artifact:// abstractions cleanly decouple client and server filesystems without protocol changes.
•Well-documented with Core Concepts, Config Reference, and working Docker Compose demo.

Weaknesses

•Hyper-specialized: only solves MCP + remote deployment gap. Won't matter until MCP adoption scales beyond Claude Desktop + early builders.
•No websocket transport support limits use cases; restricted to Streamable HTTP transport.

Post Description

I built this because MCP supports remote servers over Streamable HTTP, but a lot of MCP servers still assume the client and server share a filesystem. Once the server is in a container/VM, two things break: tools can’t read client-local file paths, and outputs (screenshots/PDFs etc) get written on the server where the client can’t access them.

Remote MCP Adapter is an application-layer gateway that sits between an MCP client and one/more upstream MCP servers. It stages inputs as upload handles and captures outputs as MCP resources that the client can read back. It also adds session isolation, automated TTL-based cleanups, quotas, state persistence, health checks and the other standard constructs necessary for a production deployment.

Docs + demo: https://aakashh242.github.io/remote-mcp-adapter/ Code: https://github.com/aakashh242/remote-mcp-adapter

Quickstart is in the README (docker compose spins up Playwright MCP + the adapter) and you point your agent at: http://localhost:8932/mcp/playwright

Would love feedback on edge cases and missing features: artifact capture rules across different servers, guarantee that all requests with a given session_id are consistently routed to the same upstream.