mcpc
The most compatible MCP CLI client. Supports: tools, resources, prompts, completions, async tasks, skills, stdio and streamable HTTP (MCP 2026-07-28 and 2025-11-25), persistent sessions, OAuth 2.1 with DCR, CIMD, client credentials, and ID-JAG, OS keychain, --json for code mode, grep for tool discovery, proxy for AI sandboxes, x402, and more.
Runssource: GitHubhomepageTypeScriptApache-2.0commit a8c34fc1af1f
TypeScript, Apache-2.0 licensed. The project labels itself: ai agents, bash, claude, cli, code mode, command line, mcp and mcp client.
mcpc runs. An Argusic agent installed it in 1 minute and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Project @apify/mcpc v0.7.0 builds from source, CLI binary prints version 0.7.0 and help text, all 1207 unit tests and 102 end-to-end tests (across two protocol versions) pass cleanly with 0 failures.
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 was installed but project requires >=22.120.5 minutes
- pnpm was not installed0.1 minutes
- Install time
- 1 minutes
- Cold machine to finish
- 18 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- ./bin/mcpc --version returned '0.7.0'; 1207 unit tests passed (vitest run, exit 0); 53 legacy + 49 modern e2e tests passed (./test/e2e/run.sh, exit 0)
- Model tokens used
- 29,156
- Exact commit tested
- a8c34fc1af1f
- 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.
exec
/bin/sh -lc 'export NVM_DIR="$HOME/.nvm" && . "$NVM_DIR/nvm.sh" && cd /work/repo && ./bin/mcpc --js…
succeeded in 0ms:
{
"sessions": [],
"profiles": []
}
All data collected. Here's my report:
2026-11-19T04:36:01.663042Z ERROR codex_core::session: failed to record rollout items: thread 01a1f…
tokens used
29,156
All data collected. Here's my report: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.
- Installed in 1 minute, faster than the median of the 123 comparable projects Argusic has measured.
- Recovered from all 2 errors 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 Apache-2.0, as reported by its host.
- Measured 2 times, so the result is not a one-off.
Of the 124 ai-agents projects Argusic has installed and timed, mcpc was the 26th fastest to reach a running state, and 96 of 124 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 1 minutes after the clone.
Also tested, in the same area
Every one of these was installed and run by Argusic on a clean machine. Nothing appears here that was not tested.
Run history
Topics (from GitHub)
ai-agentsbashclaudeclicode-modecommand-linemcpmcp-clientmodel-context-protocolshell
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcpc)Questions
- Does mcpc run?
- Yes. mcpc runs. Argusic installed and launched it on a clean machine in 1 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test mcpc?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit a8c34fc1af1f. 2 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mcpc?
- The run that produced this verdict cost $0.08: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcpc take to install?
- 1 minute in the run that decided this verdict, from a clean machine to a running state. That is one measured attempt, not an average.
- Does mcpc need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcpc?
- 2 things broke in the recorded run, and 2 were fixed without human help. Each one, and the time it cost, is listed on this page.
- How does mcpc compare with the alternatives?
- Of the 124 ai-agents projects Argusic has installed and timed, mcpc was the 26th fastest to reach a running state, and 96 of 124 reached one at all.
- Where is the evidence for mcpc?
- 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.