DevDocs
Completely free, private, UI based Tech Documentation MCP server. Designed for coders and software developers in mind. Easily integrate into Cursor, Windsurf, Cline, Roo Code, Claude Desktop App
Runs with mockssource: GitHubhomepageTypeScriptApache-2.0commit f8fa9de505c9
TypeScript, Apache-2.0 licensed. The project labels itself: cline, crawl4ai, cursor, documentation, llm, playwright, python3 and scraper.
DevDocs runs, with stand-ins for the services it depends on. An Argusic agent installed it in 5 minutes and hit 3 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Backend (FastAPI on :24125) and frontend (Next.js on :3001) both start and respond 200. The discover/crawl/crawl-status API endpoints successfully process a job from initialization through discovery_complete to completed, writing consolidated markdown and metadata files with crawl results including HTTP status codes.
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 92 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.
- Backend depends on external crawl4ai Docker container at http://crawl4ai:11235 for crawling operations3 minutes
- Python packages cannot be installed system-wide due to externally-managed-environment (PEP 668)1 minute
- Frontend .env file had a malformed concatenated line (DISCOVERY_POLLING_TIMEOUT_SECONDS=300BACKEND_URL=...) and no NEXT_PUBLIC_BACKEND_URL1 minute
- Install time
- 5 minutes
- Cold machine to finish
- 23 minutes
- Errors hit and fixed
- 3 hit, 3 fixed with no human help
- How the result was proved
- All three services ran simultaneously: mock crawl4ai returned task/completed on POST /crawl and GET /task/{id}; backend (uvicorn on :24125) answered GET /health with 200, POST /api/discover created job and completed discovery, POST /api/crawl wrote consolidated markdown files, GET /api/crawl-status returned final_status=completed, data_extracted='238 B', statusCode=200; frontend (next start on :3001) answered GET / with 200 and served 14015 byte HTML page
- Model tokens used
- 417,119
- Exact commit tested
- f8fa9de505c9
- 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
- Behaviour against real services
- this run was verified against stand-in services only
The end of the recording
The last lines of the terminal session that decided this verdict, exactly as they were recorded.
succeeded in 3918ms: FE PID=3245 HTTP Code: 200 Size: 14015 bytes Content preview: <!DOCTYPE html><html lang="en"><head><meta charSet="utf-8"/><meta name="viewport" content="width=de… All services verified successfully. Let me record the final summary exec /bin/sh -lc 'pkill -f "next start" 2>/dev/null; pkill -f "uvicorn" 2>/dev/null; pkill -f mock_crawl… exited 143 in 0ms: tokens used 417,119
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
- Installed in 5 minutes.
- Recovered from all 3 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed Apache-2.0, as reported by its host.
What did not, or is not known
- Only reached a running state against stand-in services, so nothing here proves it works against the real ones.
- Measured once so far. A single attempt shows it can run, not that it runs reliably.
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 | 1/3 | Runs with mocks | 92.00 | 0.08 |
Topics (from GitHub)
clinecrawl4aicursordocumentationllmplaywrightpython3scrapersecuritytypescriptwindsurf
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/devdocs)Questions
- Does DevDocs run?
- DevDocs runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 5 minutes, hitting 3 errors on the way, and recorded the session.
- How did Argusic test DevDocs?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit f8fa9de505c9. One attempt is recorded, and the full method is on the methodology page.
- What did it cost to test DevDocs?
- 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 DevDocs 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 DevDocs need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing DevDocs?
- 3 things broke in the recorded run, and 3 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for DevDocs?
- 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.