Ext Ops Panel
Open dashboard
Comparison

io.github.ejentum/ejentum-mcp vs GitHub MCP Server

io.github.ejentum/ejentum-mcp is an MCP server published by ejentum. Marketplaces we read that list it: 1 (Official MCP Registry). GitHub MCP Server is an MCP server published by sumirati. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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

Where each is published
Marketplaceio.github.ejentum/ejentum-mcpGitHub MCP Server
Official MCP Registry Listed
Version: 0.2.2
Downloads/month (npm): 287
Downloads/week (npm): 60
Forks (GitHub): 4
Stars (GitHub): 16
Not marked · First seen
Listed
Version: 2.2.0
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

io.github.ejentum/ejentum-mcp vs GitHub MCP Server
Factio.github.ejentum/ejentum-mcpGitHub MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)16 (better)1 (worse)
Forks (GitHub) (differs)4 (better)0 (worse)
Last release (differs)Not published2026-10-16
Where it runs (differs)Remote server (api.ejentum.com/mcp)On your machine (@sumirati/mcp-github)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 1
LicenceNot statedNot stated
Repository (differs)github.com/ejentum/ejentum-mcpgithub.com/sumirati/mcp-github
Changes in the last 7 days (differs)010
First seen (differs)2026-10-112026-10-15
Endpoint at the last check (differs)Responded 19 h agono 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

io.github.ejentum/ejentum-mcp

In its own words, on Official MCP Registry:

Reasoning, code, anti-deception, memory harness MCP tools. Stdio or HTTPS api.ejentum.com/mcp

GitHub MCP Server

In its own words, on Official MCP Registry:

Developer-ready GitHub MCP server with 5-tool hybrid architecture and dynamic discovery.

How to run each

io.github.ejentum/ejentum-mcp As a remote MCP server

Claude Code
claude mcp add --transport http ejentum-mcp https://api.ejentum.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: EJENTUM_API_KEY (secret), Authorization header

GitHub MCP Server As a local MCP server: npm package

Claude Code
claude mcp add --env "GITHUB_PERSONAL_ACCESS_TOKEN=<YOUR_GITHUB_PERSONAL_ACCESS_TOKEN>" --transport stdio mcp-github -- npx -y @sumirati/mcp-github

Requires: GITHUB_PERSONAL_ACCESS_TOKEN (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.ejentum/ejentum-mcp 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

Only io.github.ejentum/ejentum-mcp asks for

  • EJENTUM_API_KEY (secret)

Only GitHub MCP Server asks for

  • GITHUB_API_URL
  • GITHUB_EXPOSE_ALL_TOOLS
  • GITHUB_PERSONAL_ACCESS_TOKEN (secret)
  • GITHUB_READ_ONLY
  • MCP_OUTPUT_FORMAT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.ejentum/ejentum-mcp · What it can do: GitHub MCP Server · Compare two other plugins

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.

Where the data comes from: how the catalog is built