MCPJungle
One place to manage & connect to all your MCP servers
Runssource: GitHubhomepageGoMPL-2.0commit 12648be5edc7
Go, MPL-2.0 licensed. The project labels itself: ai agents, infrastructure, mcp, mcp gateway, mcp registry, mcp server, model context protocol and self hosted.
MCPJungle runs. An Argusic agent installed it in 18 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
MCPJungle builds and runs in this container: compiled binary responds to CLI commands, server starts on port 8080, health endpoint returns OK, MCP JSON-RPC endpoint responds to initialization, dashboard serves its React UI, and the full test suite passes.
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.
- Go compiler not installed in container3 minutes
- Dashboard UI bundle missing from internal/dashboardui/dist, blocking Go build2 minutes
- Install time
- 18 minutes
- Cold machine to finish
- 14 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- How the result was proved
- `go test ./...`, all 18 packages (client, cmd, internal, api, db, e2e, model, services, pkg) returned `ok` status with 341+ passing tests; `curl http://127.0.0.1:8080/health` returned `{"status":"ok"}`; `curl -X POST http://127.0.0.1:8080/mcp` with initialize payload returned valid JSON-RPC response with server info; dashboard HTML served at `/`.
- Model tokens used
- 58,316
- Exact commit tested
- 12648be5edc7
- 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 1, 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.
succeeded in 68ms: === Fresh build check === === Server version check === ███╗ ███╗ ██████╗██████╗ ██╗██╗ ██╗███╗ ██╗ ██████╗ ██╗ ███████╗ === Dashboard dist exists === internal/dashboardui/dist/index.html I have everything I need. Here's the final report: 2026-10-09T01:30:33.372439Z ERROR codex_core::session: failed to record rollout items: thread 01a11… tokens used 58,316 I have everything I need. Here's the final report: 2026-10-09T01:30:33.372718Z ERROR codex_core::session: failed to record rollout items: thread 01a11…
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 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 MPL-2.0, as reported by its host.
What did not, or is not known
- Took 18 minutes to install, slower than the median of the 123 comparable projects Argusic has measured.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 124 ai-agents projects Argusic has installed and timed, MCPJungle was the 103rd 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.
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-agentsinfrastructuremcpmcp-gatewaymcp-registrymcp-servermodel-context-protocolself-hosted
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcpjungle)Questions
- Does MCPJungle run?
- Yes. MCPJungle runs. Argusic installed and launched it on a clean machine in 18 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test MCPJungle?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 12648be5edc7. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test MCPJungle?
- The run that produced this verdict cost $0.07: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does MCPJungle take to install?
- 18 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 MCPJungle need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing MCPJungle?
- 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 MCPJungle compare with the alternatives?
- Of the 124 ai-agents projects Argusic has installed and timed, MCPJungle was the 103rd fastest to reach a running state, and 96 of 124 reached one at all.
- Where is the evidence for MCPJungle?
- The recorded run is on this page, each linking to its full log and terminal recording, stored with a sha256 fingerprint so it cannot be quietly altered.