NextBlock CMS vs Happenings Page CLI
NextBlock CMS is an MCP server published by nextblock.dev. Marketplaces we read that list it: 1 (Official MCP Registry). Happenings Page CLI is an MCP server published by happenings.social. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  NextBlock CMS |  Happenings Page CLI |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 1 Stars (GitHub): 17 Not marked · First seen |
Listed, marked deprecated Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | NextBlock CMS | Happenings Page CLI |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 17 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Not stated | Remote server (api.happenings.social/page/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/nextblock-cms/nextblock | github.com/happenings-dk/happenings-ai |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-14 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
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
NextBlock CMS
Manage pages, posts, blocks, media and settings of your self-hosted NextBlock site.
Happenings Page CLI
Every page-admin command of the Happenings CLI for your AI, limited to the pages you choose.
How to run each
NextBlock CMS
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Happenings Page CLI As a remote MCP server
claude mcp add --transport http page-cli https://api.happenings.social/page/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Happenings Page CLI 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: NextBlock CMS · What it can do: Happenings Page CLI · 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.