Ext Ops Panel
Open dashboard
Comparison

dev-journal vs VibeDNA Journal

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). VibeDNA Journal is an MCP server published by marstudio360. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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

Where each is published
Marketplacedev-journalVibeDNA Journal
Claude Code: claude-plugins-community Listed
Version: 1.0.1
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.3
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

dev-journal vs VibeDNA Journal
Factdev-journalVibeDNA Journal
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (https://github.com/marstudio360/vibedna-journal-mcp/releases/download/v1.0.3/vibedna-journal-mcp-1.0.3.mcpb)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/juliuszfedyk/dev-journalgithub.com/marstudio360/vibedna-journal-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

In its own words, on Claude Code: claude-plugins-community:

Development journal for tracking decisions, sessions, and architecture changes

VibeDNA Journal

In its own words, on Official MCP Registry:

One journal file per project that your AI reads at session start and updates as it works.

How to run each

dev-journal As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install dev-journal@claude-community

VibeDNA Journal

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

Commands 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

The marketplaces of dev-journal publish no settings it asks for, so we do not compare settings.

What it can do: dev-journal · What it can do: VibeDNA Journal · 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.

Where the data comes from: how the catalog is built