mcp-remote
Connect an MCP Client that only supports local (stdio) servers to a Remote MCP Server.
Runssource: GitHubhomepageTypeScriptMITcommit 6a06aca546a8
TypeScript, MIT licensed. The project labels itself: mcp.
mcp-remote runs. An Argusic agent installed it in 8 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
The mcp-remote TypeScript project builds to dist/ with tsup, the proxy and client binaries both report version 0.1.38, and the full test suite (490 unit tests + 8 concurrent-instance integration tests) passes under Node.js 20.18.0
What the agent ended up with on a clean machine, in its own words. How this is measured
Measured by Argusic on a fresh machine every time. Every number links to its evidence. Argusic Score 100 of 100 (the mean of this project's run scores).
At a glance
Subject data from GitHub, linked at the top of this page, refreshed . Test data by Argusic (CC BY 4.0); every number links to a run page with the full log, the recording, and their sha256 hashes.
What was measured
From the run that decided this verdict. Every line is a recorded value, not an estimate.

What went wrong, in the agent's own words
The agent's own words, worst first, never rewritten into advice.
- Node.js v18.19.1 lacks String.prototype.toWellFormed() required by undici 7.12.0, causing 12 test failures and RuntimeTypeError in fetch3 minutes
- Install time
- 8 minutes
- Cold machine to finish
- 8 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- pnpm test exited 0, 490 passed across 15 test files; pnpm vitest run concurrent-instances.test.ts exited 0, 8 passed; node dist/proxy.js --version returned 0.1.38; node dist/client.js --version returned 0.1.38
- Model tokens used
- 59,504
- Exact commit tested
- 6a06aca546a8
- Container image
- sha256:cdd920bce783
What was not measured
The other half, so you can see exactly how far this evidence goes. A gap is printed as a gap and never filled in.
- Peak GPU memory
- this ran on a CPU machine, so there was no GPU to sample
- Behaviour over a long run
- each attempt uses the smallest documented settings and a fixed time budget, so this measures whether it runs, not how it holds up under load
Watch the session
The whole run, from a clean machine, at the speed it actually happened. Nothing is cut and nothing is sped up.
A recording of attempt 2, run , the attempt that decided the verdict above. The terminal recording it was made from is the evidence, stored with a sha256 fingerprint; the video is a rendering of it. Nothing loads from the video host until you press play.
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Let me calculate the final elapsed time and produce the result: exec /bin/sh -lc 'date +%s' in /work/repo succeeded in 0ms: 1794619861 exec /bin/sh -lc 'echo "Start time ref: first test at 01:24:41, end approx 01:31"; echo "Total ~7-8 minu… succeeded in 0ms: Start time ref: first test at 01:24:41, end approx 01:31 Total ~7-8 minutes tokens used 59,504
Replay the whole session, every command from a clean machine to this point.
How it was tested
One agent, one container, no human help. It installs the project the way its own documentation says to, runs it, and fixes what breaks. Everything below is recorded as it happened: the terminal session, the log and the exact commit. The full method.
Strengths and limits
Measured facts, not opinions. How this is written.
What went well
- Reached a running state on a clean machine, with the session recorded.
- Recovered from all 1 error without a human stepping in, which says the failures are documented well enough to solve.
- Ran without a GPU, so it does not need one to start.
- Licensed MIT, as reported by its host.
- Measured 2 times, so the result is not a one-off.
What did not, or is not known
- Took 8 minutes to install, slower than the median of the 15 comparable projects Argusic has measured.
Of the 16 mcp projects Argusic has installed and timed, mcp-remote was the 14th fastest to reach a running state, and 14 of 16 reached one at all.
What it is a reasonable choice for
- Trying it on a laptop or a small server: it reached a running state without a GPU.
- A quick evaluation: it was running 8 minutes after the clone.
Run history
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcp-remote)Questions
- Does mcp-remote run?
- Yes. mcp-remote runs. Argusic installed and launched it on a clean machine in 8 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test mcp-remote?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6a06aca546a8. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mcp-remote?
- The run that produced this verdict cost $0.06: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcp-remote take to install?
- 8 minutes in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does mcp-remote need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcp-remote?
- 1 thing broke in the recorded run, and 1 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mcp-remote compare with the alternatives?
- Of the 16 mcp projects Argusic has installed and timed, mcp-remote was the 14th fastest to reach a running state, and 14 of 16 reached one at all.
- Where is the evidence for mcp-remote?
- All 2 recorded runs are on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.