mcp-server-cloudflare
Runssource: GitHubTypeScriptApache-2.0commit 1d7a16b25db7
TypeScript, Apache-2.0 licensed.
mcp-server-cloudflare runs. An Argusic agent installed it in 5 minutes and hit 1 error and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Monorepo installs cleanly with Node 22; full test suite passes; demo-day MCP server starts locally and answers Streamable HTTP tools/list requests.
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 18 lacks global File API required by undici/workerd3 minutes
- Install time
- 5 minutes
- Cold machine to finish
- 6 minutes
- Errors hit and fixed
- 1 hit, 1 fixed with no human help
- How the result was proved
- pnpm test: 36 passed / 339 passed. curl -X POST localhost:8888/mcp with Accept header returned 200 and valid MCP tools/list response.
- Model tokens used
- 24,580
- Exact commit tested
- 1d7a16b25db7
- 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
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
- `POST /mcp` with `Accept: application/json, text/event-stream` returned **200 OK** with a valid `… 2026-09-30T10:22:33.212946Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… 2026-09-30T10:22:33.213262Z ERROR codex_core::session: failed to record rollout items: thread 01a0f… tokens used 24,580 The server is running correctly and responds with proper MCP protocol. Now let me compile the final… Here's the full record of what was done and observed: **Install**: `pnpm install` completed successfully with all 865+ packages. **Node upgrade**: The container had Node 18, which lacks the global `File` API required by `undici`… **Tests**: `pnpm test` with Node 22 → **36 test files passed, 339 tests passed** (0 failures). **App launch**: Ran `wrangler dev` on the demo-day server. Verified the MCP endpoint works: - `POST /mcp` with `Accept: application/json, text/event-stream` returned **200 OK** with a valid `…
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 5 minutes.
- 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 Apache-2.0, as reported by its host.
What did not, or is not known
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
Of the 20 TypeScript projects Argusic has installed and timed, mcp-server-cloudflare was the 9th fastest to reach a running state, and 17 of 20 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 5 minutes after the clone.
Run history
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/mcp-server-cloudflare)Questions
- Does mcp-server-cloudflare run?
- Yes. mcp-server-cloudflare runs. Argusic installed and launched it on a clean machine in 5 minutes, hitting 1 error on the way, and recorded the session.
- How did Argusic test mcp-server-cloudflare?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 1d7a16b25db7. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test mcp-server-cloudflare?
- The run that produced this verdict cost $0.03: real compute and model cost, not a list price per million tokens. It is recorded on that run's page.
- How long does mcp-server-cloudflare take to install?
- 5 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-server-cloudflare need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing mcp-server-cloudflare?
- 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-server-cloudflare compare with the alternatives?
- Of the 20 TypeScript projects Argusic has installed and timed, mcp-server-cloudflare was the 9th fastest to reach a running state, and 17 of 20 reached one at all.
- Where is the evidence for mcp-server-cloudflare?
- 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.