dev-journal vs miro
dev-journal is a plugin bundle for AI coding tools published by juliuszfedyk. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). miro is a plugin bundle for AI coding tools published by miroapp. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-18. 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 |  dev-journal |  miro |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.3.0 Forks (GitHub): 21 Stars (GitHub): 163 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 2.0.0 Forks (GitHub): 21 Stars (GitHub): 163 Not marked · First seen |
| Claude: knowledge-work-plugins | Not listed | Listed Version: 2.0.0 Forks (GitHub): 21 Stars (GitHub): 163 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 | dev-journal | miro |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 4 (better) |
| Stars (GitHub) (differs) | 1 (worse) | 163 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 21 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.miro.com) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | 8 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/juliuszfedyk/dev-journal | github.com/miroapp/miro-ai |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 2 days ago, requires a key |
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
dev-journal
Development journal for tracking decisions, sessions, and architecture changes
miro
Secure access to Miro boards. Enables AI to read board context, create diagrams, and generate code with enterprise-grade security.
How to run each
dev-journal As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dev-journal@claude-communitymiro As a Claude Code plugin
/plugin install miro@claude-plugins-officialCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only miro 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: dev-journal · What it can do: miro · 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 public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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.