mcp-context-forge
An AI Gateway, registry, and proxy that sits in front of any MCP, A2A, or REST/gRPC APIs, exposing a unified endpoint with centralized discovery, guardrails and management. Optimizes Agent & Tool calling, and supports plugins.
Runssource: GitHubhomepagePythonApache-2.0commit 1c198de701e8
Python, Apache-2.0 licensed. The project labels itself: agents, ai, api gateway, asyncio, authentication middleware, devops, docker and fastapi.
mcp-context-forge runs. An Argusic agent installed it in 33 minutes and hit 2 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
ContextForge gateway installed in .venv, server launches and responds on HTTP, 592+ unit tests pass against real SQLite and auth infrastructure.
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.
- npm build-ui failed: Node.js 18.19.1 too old for Vite 7.x (requires >=20.19.0)3 minutes
- make check-env validates .env.example instead of .env, causing false positive failure2 minutes
- Install time
- 33 minutes
- Cold machine to finish
- 32 minutes
- Errors hit and fixed
- 2 hit, 2 fixed with no human help
- Model tokens used
- 208,582
- Exact commit tested
- 1c198de701e8
- 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.
- How the result was proved
- runs before 2026-09-07 did not record the command used to check the result
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
Here's my final report: **Summary of work completed:** 1. **`uv` installed** via `pip install --user --break-system-packages` (no apt access as non-root) 2. **`.env` configured**: copied from `.env.example`, secrets generated with `init_secrets --patch-… 3. **`make install-dev`** succeeded for Python dependencies (299 packages) but the Admin UI build (… 4. **App imports and loads**: `python -c "import mcpgateway"` works 5. **Server launches**: uvicorn starts on port 8000/8001, responds to HTTP requests with appropriat… 6. **Unit tests pass**: 592+ tests passing across `test_version.py`, `test_config.py`, `test_db.py`… 7. Only the `make check-env` target has a bug (validates `.env.example` instead of `.env`) — this i… **Errors encountered:** - **Error 1**: `npm build-ui` failed due to Node.js 18.19.1 < 20.19.0 required by Vite 7.x. Fix: sk… - **Error 2**: `make check-env` validates `.env.example` (which has placeholders) instead of `.env`…
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 Apache-2.0, as reported by its host.
- Measured 3 times, so the result is not a one-off.
What did not, or is not known
- Took 33 minutes to install, slower than the median of the 7 comparable projects Argusic has measured.
Of the 8 agents projects Argusic has installed and timed, mcp-context-forge was the 8th fastest to reach a running state, and 5 of 8 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
| tested by | attempt | outcome | score | cost USD | when |
|---|---|---|---|---|---|
| Argusic Runner | 2/3 | Runs | 100.00 | 0.13 | |
| Argusic Runner | 1/3 | Ran out of time | 0.00 | 0.17 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.11 |
Topics (from GitHub)
agentsaiapi-gatewayasyncioauthentication-middlewaredevopsdockerfastapifederationgatewaygenerative-aijwtkubernetesllm-agentsmcpmodel-context-protocolobservabilityprompt-engineeringpythontools
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcp-context-forge)Questions
- Does mcp-context-forge run?
- Yes. mcp-context-forge runs. Argusic installed and launched it on a clean machine in 33 minutes, hitting 2 errors on the way, and recorded the session.
- How did Argusic test mcp-context-forge?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1c198de701e8. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test mcp-context-forge?
- The run that produced this verdict cost $0.13: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcp-context-forge take to install?
- 33 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-context-forge need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcp-context-forge?
- 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 mcp-context-forge compare with the alternatives?
- Of the 8 agents projects Argusic has installed and timed, mcp-context-forge was the 8th fastest to reach a running state, and 5 of 8 reached one at all.
- Where is the evidence for mcp-context-forge?
- All 3 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.