mcp-logseq vs GEML — a plain-text document format built to be edited in place, one section at a time
mcp-logseq is an MCP server published by ergut. Marketplaces we read that list it: 1 (PyPI (MCP servers)). GEML — a plain-text document format built to be edited in place, one section at a time is an MCP server published by geml-spec. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-10. 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 |  mcp-logseq |   GEML — a plain-text document format built to be edited in place, one section at a time |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 1.10.0 Downloads/month (PyPI): 1 891 Downloads/week (PyPI): 152 Forks (GitHub): 51 Stars (GitHub): 350 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.13.1 Downloads/month (npm): 1 587 Downloads/week (npm): 235 Forks (GitHub): 4 Stars (GitHub): 31 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.13.1 Downloads/month (npm): 1 587 Downloads/week (npm): 235 Forks (GitHub): 4 Stars (GitHub): 31 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 | mcp-logseq | GEML — a plain-text document format built to be edited in place, one section at a time |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 350 (better) | 31 (worse) |
| Forks (GitHub) (differs) | 51 (better) | 4 (worse) |
| Last release (differs) | Not published | 2026-11-10 |
| Where it runs (differs) | On your machine (mcp-logseq) | Remote server or your machine |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | MIT | MIT |
| Repository (differs) | github.com/ergut/mcp-logseq | github.com/geml-spec/geml |
| Changes in the last 7 days (differs) | 0 | 5 |
| First seen (differs) | 2026-10-12 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 34 h ago returned HTTP 405 |
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
mcp-logseq
MCP server to work with LogSeq via the local HTTP server
GEML — a plain-text document format built to be edited in place, one section at a time
One section in, one section out — on Markdown/GEML files, bad writes refused.
How to run each
mcp-logseq
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
GEML — a plain-text document format built to be edited in place, one section at a time As a remote MCP server
claude mcp add --transport http geml https://geml-mcp.supermarket.workers.dev/mcpRequires: --root
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only GEML — a plain-text document format built to be edited in place, one section at a time has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of mcp-logseq nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: mcp-logseq · What it can do: GEML — a plain-text document format built to be edited in place, one section at a time · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). 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.