io.github.ejentum/ejentum-mcp vs io.github.koki-develop/esa-mcp-server
io.github.ejentum/ejentum-mcp is an MCP server published by ejentum. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.koki-develop/esa-mcp-server is an MCP server published by koki-develop. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  io.github.ejentum/ejentum-mcp |  io.github.koki-develop/esa-mcp-server |
|---|---|---|
| Official MCP Registry | Listed Version: 0.2.2 Downloads/month (npm): 251 Downloads/week (npm): 26 Forks (GitHub): 4 Stars (GitHub): 16 Not marked · First seen |
Listed Version: 0.3.2 Downloads/month (npm): 135 Downloads/week (npm): 17 Forks (GitHub): 0 Stars (GitHub): 2 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 | io.github.ejentum/ejentum-mcp | io.github.koki-develop/esa-mcp-server |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 16 (better) | 2 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.ejentum.com/mcp) | On your machine (@koki-develop/esa-mcp-server) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/ejentum/ejentum-mcp | github.com/koki-develop/esa-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-26 | 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
io.github.ejentum/ejentum-mcp
Reasoning, code, anti-deception, memory harness MCP tools. Stdio or HTTPS api.ejentum.com/mcp
io.github.koki-develop/esa-mcp-server
A Model Context Protocol (MCP) server for esa.io
How to run each
io.github.ejentum/ejentum-mcp As a remote MCP server
claude mcp add --transport http ejentum-mcp https://api.ejentum.com/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: EJENTUM_API_KEY (secret), Authorization header
io.github.koki-develop/esa-mcp-server As a local MCP server: npm package
claude mcp add --env "ESA_ACCESS_TOKEN=<YOUR_ESA_ACCESS_TOKEN>" --env "ESA_TEAM=<YOUR_ESA_TEAM>" --transport stdio esa-mcp-server -- npx -y @koki-develop/esa-mcp-serverRequires: ESA_ACCESS_TOKEN (secret), ESA_TEAM
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 io.github.koki-develop/esa-mcp-server asks for
ESA_ACCESS_TOKEN (secret)ESA_TEAM
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: io.github.koki-develop/esa-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.