bloom vs Markdown to Word
bloom is a plugin bundle for AI coding tools published by SunnyDevendranadh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Markdown to Word is an MCP server published by benbalter. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 |  bloom |  Markdown to Word |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.4.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.4.0 Forks (GitHub): 1 Stars (GitHub): 1 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 | bloom | Markdown to Word |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 1 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (markdown-to-word) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/sunnydevendranadh/html.md | github.com/benbalter/markdown-to-word-js |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-19 |
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
bloom
Sticky session mode that turns flat markdown into rich, self-contained .html artifacts. Activate with /bloom once and every substantial output for the rest of the session — status reports, PR reviews, design docs, comparisons, plans, diagrams, slide decks, postmortems, triage boards, flag and prompt editors — becomes a single browsable .html file with semantic HTML5, inline CSS/JS, and zero external dependencies. Reserved files like README.md, CLAUDE.md, and AGENTS.md keep their canonical markdown and gain a richer .html companion next to them. Deactivate with /bloom-off at any time.
Markdown to Word
Convert GitHub Flavored Markdown to Word (.docx) documents in Node or the browser
How to run each
bloom As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install bloom@claude-communityMarkdown to Word As a local MCP server: npm package
claude mcp add --transport stdio markdown-to-word -- npx -y markdown-to-word mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
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: bloom · What it can do: Markdown to Word · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.