Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer
VibeDNA Journal
Overview
Description from the maker (original English)
One journal file per project that your AI reads at session start and updates as it works.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiVery new★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
JOURNAL_ROOTS,JOURNAL_HOME
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Download the maker’s .mcpb file
The link goes to the maker’s own file; we do not host or repackage it. Open the file and Claude Desktop installs it.
Run this in your terminal
Fill in the empty values before running it.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
JOURNAL_ROOTSenvFolders to scan for *JOURNAL.md files, separated by ;JOURNAL_HOMEenvWhere the local search index lives. Default ~/.journal
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 9, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account marstudio360, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 18728 servers in this category
- Published to the registry more recently than 58% of the other 18728 servers in this category
- Basic checks equal to or better than 100% of the other 18728 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is VibeDNA Journal safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (1.0.3) reached the registry 34 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need MCPB on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, Shield Kya
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud✓ desktopcommander.app
Shield Kya
Audit trail and traceability for AI agents. MCP gate: evaluate, ingest, request approval.
Runs on your computer
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Journals DNA
Your AI cannot skip your journal.
Journals DNA gives every project one markdown journal ( _JOURNAL.md) that your AI reads before it acts and writes to while it works. The next session, or another AI, picks up exactly where the last one stopped, and you can share your work with anyone by sending the journal.
It runs on your machine. Your journals stay where they are, in plain markdown.
What it does, in plain words
- Journals your AI must read. In Claude Code, the journals mod stops the first edit of a piece of your project until the AI has really read that piece's journal. A plain retry does not get through; reading the journal does.
- A map before every change. Before your AI edits a file, runs a command or briefs an agent, it sees a short map of that thing: which journal talks about it, who is working on it now, what was already decided, what already exists, the latest entries and what is still pending.
- It warns when your AI repeats itself. When the AI is about to build its own way of doing a job a tool you already have does, it is shown that tool and stopped once. When a reply proposes something your journals already have a verdict on, or lists as pending something a journal says shipped, the AI is told so in its next turn.
- It warns about stale status. Lines that state something that changes (an account is active, a service is live, a balance) are marked "check live before repeating it" in the map. When the AI writes an entry that states such a status without saying how it was checked, the entry is still saved and the AI gets a warning.
- Your rules, in your words. Write your rules as dated lines in a rules journal (
RULES_JOURNAL.mdor any*_RULES_JOURNAL.md). When an action shares the words of a rule, the rule is shown and the action stops once. - Finds what you meant, in any language (optional). A small model on your own processor gives every entry a meaning, so a question in other words or another language finds the entry that says the same thing. Your journals never leave your computer.
- Old decisions never pass as current. When a later entry replaced a decision, or states a different price or number for it, the decision is shown with that newer line first and your AI checks the live source and updates it.
- It stops rebuilding what already exists. Before your AI writes a new script or briefs an agent to build something a shipped entry already did, it is shown that entry and stopped once.
- Your decisions guard the reply (optional). Each project gets an owner brief: your rules, what you already tried and lost, and the thread you approved. With the reply check on, a reply that proposes again what you rejected, or describes one of your tools against its own sheet, is sent back for a rewrite before you read it.
- Old rules carry their newer word. A rule or decision older than a week is shown with the newer entry that changed it, so your AI never follows an outdated rule as current.
- A calm status line. Under your prompt:
Journals DNA · active, and one plain sentence only when something real happens. - Opens in Obsidian. One command builds a map of all your journals for Obsidian: a START HERE page, a table view of every journal, and a canvas by folder. New journals are born with Obsidian properties.
What is inside
| Part | What it is |
|---|---|
server.py | The journal MCP server: 35 tools to read, search, write and keep journals (works with any MCP client) |
quickmap.py, quick_hook.py | The quick map and the checks the mod runs (local, no network; no AI unless you switch the judge on) |
judge.py, owner_brief.py | Optional: the judge (your claude command decides what is really relevant) and the owner brief of each project |
toolmap.py, tool_concepts.json | "A tool already does this": matches an action to the tools and flows your journals list |
livecopy.py, ruledupes.py | Warnings for a command on the wrong copy of a deployed folder, and for a rule written twice |
obsidian.py | Builds the Obsidian map of your journals |
meaning.py, builtmap.py | Search by meaning (optional, local model) and the "already built" check |
embed_server.py | Optional: one shared embedding service on a team GPU machine |
mod/ | The journals mod, a Claude Code plugin |
install_mod.py | One command that installs the server and the mod in Claude Code, and undoes it |
examples/DEMO_PROJECT.md | A small journal to try everything on (copy it as DEMO_JOURNAL.md into a test folder) |
BRAIN_MAP_TEMPLATE.md, RULES_TEMPLATE.md | Copy-paste starting points |
New in 1.4.0
- A calm status line:
Journals DNA · active, one plain sentence per real event, never internal wording. - Newer word on old rules: an old rule or decision is shown with the newer entry that changes it.
- The reply check against your own decisions (opt in:
JOURNAL_REPLY_GATE=onwith the judge on): a reply that breaks your rules or proposes again what you already lost is sent back before you read it, with the words quoted. - Judged manual hints: a lesson is pointed at one of your manuals only when the judge agrees it belongs there.
- Your own tools in
tools.json: a message that names one carries what it does today. - The judge is optional and off by default; without it the checks fall back to the rules of 1.3.0. See INSTALL.md.
Install
Full steps, written so you can hand the file to your AI: INSTALL.md. Short version, from this folder:
python3 -m venv .venv.venv/bin/pip install -r requirements.txt # Windows: .venv\Scripts\pip install -r requirements.txt .venv/bin/python install_mod.py --dry-run # Windows: .venv\Scripts\python install_mod.py --dry-run .venv/bin/python install_mod.py # Windows: .venv\Scripts\python install_mod.py
Then open a new Claude Code session and ask: journal_quick(" ").
Other MCP clients (Cursor and others) can run server.py as a normal MCP server; the mod and its stops are a Claude Code feature.
The tools
| Group | Tools |
|---|---|
| Start and read | journal_handoff_brief, journal_read (line ranges), journal_read_section, journal_list_sections, journal_list |
| Find | journal_quick, journal_search, journal_before_build, journal_recent_changes, journal_map |
| Write | journal_append, journal_update_section, journal_create, journal_decision_add, journal_capability_add |
| Keep it true | journal_verify (re-run check: lines), journal_audit, journal_contradictions, journal_overlap_check, journal_stats |
| Setup | journal_how_to, journal_index_refresh, journal_config_add_root, journal_install_rule, journal_get_claude_rule, journal_install_build_check, journal_backup_to_drive |
| Store | journal_pair, journal_market, journal_get, journal_library, journal_browse, journal_market_index, check_for_update, vibedna_info |
Open your journals in Obsidian
.venv/bin/python obsidian.py vault --root "<your projects folder>" # dry run: lists what it would write.venv/bin/python obsidian.py vault --root " " --apply # writes it
It writes _obsidian/START HERE.md, _obsidian/Journals.base, _obsidian/Journals map.canvas and a minimal .obsidian/ config in that folder, then you open the folder as a vault in Obsidian. Details in INSTALL.md.
Your data
Everything is local: the journals are your files, the index lives in ~/.journal. The quick map and the mod make no network calls. The store tools (journal_market, journal_get, ...) and check_for_update talk to vibedna.ai only when you call them. See SECURITY.md.
Vibedna, vibedna.ai