GitHub vs io.github.infino-ai/code-context
GitHub is an MCP server published by github. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). io.github.infino-ai/code-context is an MCP server published by infino-ai. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-13. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.2 Forks (GitHub): 5 134 Stars (GitHub): 33 552 Not marked · First seen |
Listed Version: 0.5.1 Downloads/month (npm): 584 Downloads/week (npm): 77 Forks (GitHub): 1 Stars (GitHub): 31 Not marked · First seen |
| Docker MCP Catalog | Listed Version: sha256:ffced0d76e77 Forks (GitHub): 5 134 Stars (GitHub): 33 552 Not marked · First seen |
Not listed |
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 | io.github.infino-ai/code-context |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 33 552 (better) | 31 (worse) |
| Forks (GitHub) (differs) | 5 134 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server or your machine | On your machine (@infino-ai/code-context) |
| Transport (differs) | Streamable HTTP, stdio | stdio |
| Tools it declares (differs) | 40 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 5, secrets among them: 0 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/github/github-mcp-server | github.com/infino-ai/code-context |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
GitHub
Connect AI assistants to GitHub - manage repos, issues, PRs, and workflows through natural language.
io.github.infino-ai/code-context
Local code search for AI coding agents: hybrid keyword + semantic + SQL over an index in your repo.
How to run each
GitHub As a remote MCP server
claude mcp add --transport http github-mcp-server https://api.githubcopilot.com/mcp/ --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
io.github.infino-ai/code-context As a local MCP server: npm package
claude mcp add --transport stdio code-context -- npx -y @infino-ai/code-context mcp
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.infino-ai/code-context publish no list of tools, so we do not compare tools.
Settings each asks for
Only GitHub asks for
GITHUB_PERSONAL_ACCESS_TOKEN (secret)
Only io.github.infino-ai/code-context asks for
CX_AUTO_SYNCCX_INDEX_DIRCX_NO_EMBEDCX_NO_RECEIPTCX_PLATFORM_URLCX_ROOT
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: GitHub · What it can do: io.github.infino-ai/code-context · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.