microcms-mcp-server vs vibecms
microcms-mcp-server is an MCP server published by microcmsio. Marketplaces we read that list it: 1 (npm registry (MCP servers)). vibecms is an MCP server published by vibecms.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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 |  microcms-mcp-server |  vibecms |
|---|---|---|
| npm registry (MCP servers) | Listed Version: 0.12.0 Downloads/month (npm): 3 655 Downloads/week (npm): 1 267 Forks (GitHub): 9 Stars (GitHub): 22 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Forks (GitHub): 1 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 | microcms-mcp-server | vibecms |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 22 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 9 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (microcms-mcp-server) | Remote server (app.vibecms.dev/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/microcmsio/microcms-mcp-server | github.com/moinulmoin/vibecms |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-12 | 2026-11-01 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 24 h 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
microcms-mcp-server
microCMS MCP Bundle - microCMSのコンテンツAPIやマネジメントAPIを利用し、LLMからコンテンツ管理ができるMCP Bundle
vibecms
A blog CMS that AI agents write into over MCP: Markdown drafts, versions, media, human approval.
How to run each
microcms-mcp-server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
vibecms As a remote MCP server
claude mcp add --transport http vibecms https://app.vibecms.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only vibecms 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: microcms-mcp-server · What it can do: vibecms · Compare two other plugins
Package data comes from the public npm registry (registry.npmjs.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.