repocritics-mcp-server

An MCP server that gives an agent read access to the RepoCritics corpus: community-written summaries of open-source repositories, plus the scores and reviews behind them.

The point is that the summarising has already happened. Asking "is this library still maintained, and what do people actually complain about?" normally means reading a README, skimming a release feed, and sampling four issue threads. Here it is one call that returns a page someone already wrote.

Read-only, no API key, free.

Install

Claude Code — nothing to install first:

claude mcp add repocritics -- npx -y repocritics-mcp-server

Anything else — add to your client's MCP config:

{
  "mcpServers": {
    "repocritics": {
      "command": "npx",
      "args": ["-y", "repocritics-mcp-server"]
    }
  }
}

Or install it globally and drop the npx:

npm install -g repocritics-mcp-server

No configuration follows. The server talks to the public REST API over HTTPS; nothing is stored locally and no credentials are involved.

Tools

| Tool | What it returns | |------|-----------------| | search_repos | Full-text search across the corpus. query, optional category, tag, limit. | | get_wiki | The community wiki page for one repository. platform, owner, name. | | get_repo | Metadata and scores for one repository. Same arguments. | | list_related | Repositories adjacent to this one, ranked by shared-topic overlap, each edge carrying the topics that produced it. Same, plus limit. | | list_reviews | Community reviews for one repository. Same, plus limit. | | list_categories | Every category with the tag filters that define it. | | list_tags | Tag vocabulary across the corpus, most frequent first. Optional limit. | | get_ai_report | A cached deep-analysis report, when one exists for the repository. |

get_wiki is the one worth reaching for first — it is the summarised form the whole project exists to produce. list_related is how you keep going: the wiki pages carry no links of their own, so this is the only way to move from one to the next rather than starting a new search each time.

Resources

| URI | Content | |-----|---------| | repocritics://wiki/{platform}/{owner}/{name} | Wiki page as markdown | | repocritics://reviews/{platform}/{owner}/{name} | Reviews as JSON | | repocritics://feed/global | Atom feed of recent review activity |

Coverage

The corpus is seeded, not exhaustive — roughly two thousand repositories at the time of writing. search_repos is the cheapest way to check whether something is present before asking for it by name; a miss comes back as an explicit "not in the corpus" rather than an empty page.

Rate limits

100 requests per endpoint per day, per IP. No key, so nothing to rotate.

Responses are edge-cached, and a cached response never reaches the counter — repeated reads of the same page are effectively free. In practice the ceiling is only met by walking the corpus with a fresh query each time, which is what it is there for.

Going over returns a plain message with the time until the quota resets. If the limit is genuinely in your way, open an issue.

Configuration

| Variable | Default | Purpose | |----------|---------|---------| | REPOCRITICS_API_BASE | https://repocritics.com/api/v1 | Point at a local or staging deployment |

Using the data

Wiki pages are written by contributors at github.com/repocritics/wiki and licensed CC-BY-SA 4.0. Quote them, build on them, feed them to a model — attribute RepoCritics and link back.

The API is also described as OpenAPI 3.1 and advertised through an ARD catalog, if you would rather call it directly than through MCP.

Development

npm install
npm run build
npm run dev      # run from source

License

MIT — see LICENSE. Wiki content is CC-BY-SA 4.0 and licensed separately.