context7
Context7 Platform -- Up-to-date code documentation for LLMs and AI code editors
Runs with mockssource: GitHubhomepageTypeScriptMITcommit 6d777619c277
TypeScript, MIT licensed. The project labels itself: llm, mcp, mcp server and vibe coding.
context7 runs, with stand-ins for the services it depends on. An Argusic agent installed it in 6 minutes and hit 5 errors and fixed every one without help on a clean machine with no GPU, and the whole session was recorded.
Build succeeds on all 6 packages. Test suites pass for CLI (361), MCP (59), SDK (27 with mock), and PI (4). The tools-ai-sdk has 11 of 16 tests passing; 5 require real AWS Bedrock credentials. The ctx7 CLI binary and MCP server both launch and respond correctly.
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 87.7 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.
- SDK tests required CONTEXT7_API_KEY and hit live API2 minutes
- Node.js v18 lacked features required by dependencies (styleText, undici File, 'v' regex flag)1 minute
- pnpm not installed1 minute
- pnpm-workspace.yaml had string placeholders instead of booleans for allowBuilds
- 5 tools-ai-sdk tests need AWS Bedrock credentials (AWS_REGION)
- Install time
- 6 minutes
- Cold machine to finish
- 10 minutes
- Errors hit and fixed
- 5 hit, 5 fixed with no human help
- How the result was proved
- pnpm test across all packages: CLI 361/361 passed, MCP 59/59 passed, SDK 27/27 passed (with mock), PI 4/4 passed, tools-ai-sdk 11/16 passed (5 need AWS Bedrock); ctx7 --help prints all commands; MCP server responds to tools/list
- Model tokens used
- 87,462
- Exact commit tested
- 6d777619c277
- 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.
| Package | Files | Tests | Status | |---|---|---|---| | CLI (`ctx7`) | 17 | 361 | All passed | | MCP (`@upstash/context7-mcp`) | 6 | 59 | All passed | | SDK (`@upstash/context7-sdk`) | 4 | 27 | All passed (mock API in setup) | | PI (`@upstash/context7-pi`) | 1 | 4 | All passed | | tools-ai-sdk (`@upstash/context7-tools-ai-sdk`) | 1 | 16 | 11 passed, 5 failed | **Remaining failures**: 5 tests in `@upstash/context7-tools-ai-sdk` need `AWS_REGION` and AWS Bedro… **Binaries verified** - `ctx7 --help`: all commands listed - MCP server: responds correctly to `tools/list` JSON-RPC request **Mock**: Created a `packages/sdk/src/test-setup.ts` that sets `CONTEXT7_API_KEY` and mocks `fetch`…
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 6 minutes.
- Recovered from all 5 errors without a human stepping in, which says the failures are documented well enough to solve.
- Licensed MIT, as reported by its host.
- Measured 3 times, so the result is not a one-off.
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.
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 | 3/3 | Runs with mocks | 92.00 | 0.07 | |
| Argusic Runner | 1/3 | Runs with mocks | 83.43 | 0.10 | |
| Argusic Runner | 2/3 | Ran out of time | 0.00 | 0.07 |
Topics (from GitHub)
Embed the badge
Markdown for the project README. It links back here; terms on the terms page.
[](https://argusic.com/subject/context7)Questions
- Does context7 run?
- context7 runs, with mocks standing in for external services. Argusic installed and launched it on a clean machine in 6 minutes, hitting 5 errors on the way, and recorded the session.
- How did Argusic test context7?
- On a fresh, disposable machine, with every command recorded and the repository pinned at commit 6d777619c277. 3 attempts are recorded, and the full method is on the methodology page.
- What did it cost to test context7?
- 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 context7 take to install?
- 6 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 context7 need a GPU?
- Not to start. Argusic reached a running state on a machine with no GPU.
- What goes wrong when installing context7?
- 5 things broke in the recorded run, and 5 were fixed without human help. Each one, and the time it cost, is listed on this page.
- Where is the evidence for context7?
- 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.