github-librarian vs GitHub Repository Intelligence
github-librarian is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
github-librarian is a plugin bundle for AI coding tools published by diegopetrucci. No marketplace we read lists it any more. GitHub Repository Intelligence is an MCP server published by heisencodex-jpg. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-29. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  GitHub Repository Intelligence | |
|---|---|---|
| Community marketplace diegopetrucci/ai-agents-skills | Removed on 2026-10-19 Version: 1.1.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.3.1 Forks (GitHub): 0 Stars (GitHub): 1 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 | github-librarianno longer listed · | GitHub Repository Intelligence |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (cg-nguyen--github-repo-intel-mcp.apify.actor/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 3 | Not a bundle |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/diegopetrucci/github-librarian | github.com/heisencodex-jpg/github-repo-intel-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not responding since 2026-10-26 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of github-librarian
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Tools for interacting with Git repositories.
-
A Model Context Protocol (MCP) for analyzing and querying GitHub repositories using the GitHub Chat API.
-
Octocode MCP - AI Context Platform
AI code research platform. Search, analyze, and extract insights from any GitHub repository.
-
Inspect repositories, triage pull requests and issues, debug CI, and publish changes through a hybrid GitHub connector and CLI workflow.
-
Fast, bounded, read-only Git evidence for local AI coding agents.
-
Official GitHub MCP server for repository management. Create issues, manage pull requests, review code, search repositories, and interact with GitHub's full API directly from…
What each says it does
github-librarian
Investigate GitHub via `gh` in an isolated subagent and return concise, path-first findings with line-ranged evidence
GitHub Repository Intelligence
Repo intel for AI coding agents: overview, PRs, contributors, hot files, CI, deps. Remote MCP.
How to run each
github-librarian
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
GitHub Repository Intelligence As a remote MCP server
claude mcp add --transport http github-repo-intel-mcp https://cg-nguyen--github-repo-intel-mcp.apify.actor/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GitHub Repository Intelligence 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
Neither one's marketplaces publish the settings it asks for.
What it can do: github-librarian · What it can do: GitHub Repository Intelligence · 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.