devharness vs Context7
devharness is a plugin bundle for AI coding tools published by InDate. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Context7 is an MCP server published by upstash. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |   Context7 | |
|---|---|---|
| Community marketplace indate/devharness | Listed Version: not stated Forks (GitHub): 5 Stars (GitHub): 18 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 4.4.4 Downloads/month (npm): 2 685 137 Downloads/week (npm): 561 384 Forks (GitHub): 3 127 Stars (GitHub): 63 497 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | devharness | Context7 |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 18 (worse) | 63 497 (better) |
| Forks (GitHub) (differs) | 5 (worse) | 3 127 (better) |
| Last release (differs) | Not published | 2026-10-19 |
| Where it runs (differs) | On your machine (devharness) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 3 | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/indate/devharness | github.com/upstash/context7 |
| Changes in the last 7 days (differs) | 2 | 9 |
| First seen (differs) | 2026-10-22 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
devharness
Run and debug a live app from inside Claude Code. Installed from the working tree: the plugin manifest, its skill and its hooks are whatever is on disk right now.
Context7
Up-to-date docs for AI agents
How to run each
devharness As a Claude Code plugin
/plugin marketplace add indate/devharness
/plugin install devharness@devharness-localContext7 As a remote MCP server
claude mcp add --transport http context7 https://mcp.context7.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: CONTEXT7_API_KEY (secret), Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Context7 has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of devharness publish no settings it asks for, so we do not compare settings.
What it can do: devharness · What it can do: Context7 · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.