mcp-logseq vs dylog
mcp-logseq is an MCP server published by ergut. Marketplaces we read that list it: 1 (PyPI (MCP servers)). dylog is an MCP server published by imjakezimmer32. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  dylog |
|---|---|---|
| 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.0.2 No figure published 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 | dylog |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 350 | No figure on GitHub |
| Forks (GitHub) (differs) | 51 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-logseq) | Remote server (dylog.app/api/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/ergut/mcp-logseq | github.com/imjakezimmer32/talkmill |
| Changes in the last 7 days | 0 | 0 |
| 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 47 h ago returned HTTP 200 |
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
dylog
Notes, files, GitHub, and Drive through one MCP connection.
How to run each
mcp-logseq
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
dylog As a remote MCP server
claude mcp add --transport http dylog https://dylog.app/api/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 dylog 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: mcp-logseq · What it can do: dylog · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.