Journal MCP
Allows copying journal files to a user-configured rclone remote for optional backup.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Journal MCPcatch me up on the journal for my api-gateway project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
VibeDNA Journal MCP
One journal file per project that your AI reads at session start and updates as it works.
Journal gives every project one plain markdown file (*_JOURNAL.md). Your AI reads it when a session starts and appends to it as work ships: decisions with their reasons, bugs with root cause and fix, current state, roadmap, and a handoff note for the next session. Ranked full-text search finds an entry across every project's journal at once. One optional tool adds a rule to your CLAUDE.md so Claude Code keeps the habit without being asked.
Runs locally over stdio. Python 3.10+ and the
mcppackage.The journaling core makes no network calls. Your journals stay on your disk.
Optional marketplace tools browse and download journals from vibedna.ai, only when you call them.
Homepage: https://vibedna.ai/store/journal
Tools (25)
Catch up on a project
Tool | What it does |
| Short catch-up: header plus the latest entries |
| Full journal contents |
| One section, e.g. |
| The H2 sections of a journal |
| List the journals in the index |
Log work as it ships
Tool | What it does |
| Timestamped entry |
| Replace, append or prepend a section |
| New journal with the standard sections |
Search
Tool | What it does |
| Ranked full-text search (SQLite FTS5) across all journals, with snippets |
| Journals updated lately |
| Totals, biggest and freshest journals |
| Browse the local library by metadata |
| Local feed of journals of one kind, with metadata |
| Find journals that overlap with this one |
Setup
Tool | What it does |
| Rescan the roots for journal files |
| Add a folder to scan |
| The recommended |
| Install that rule (preview unless |
| Copy journals to your own rclone remote (optional) |
| Compare this copy with the published version |
| Product metadata |
Marketplace (optional, reaches vibedna.ai)
Tool | What it does |
| Browse the VibeDNA journal shelf |
| Link this install to a vibedna.ai account |
| Download a journal you own, or get a checkout link for one you don't |
| List the journals you own |
Related MCP server: LumenCore
Install
git clone https://github.com/marstudio360/vibedna-journal-mcp
cd vibedna-journal-mcp
pip install -r requirements.txtJOURNAL_ROOTS is the list of folders to scan for journal files, separated by ;. Without it, Journal scans ~/Desktop and ~/Documents.
Claude Code
claude mcp add journal --scope user -e JOURNAL_ROOTS="/path/to/your/projects" -- python /absolute/path/to/vibedna-journal-mcp/server.pyOr in a project's .mcp.json:
{
"mcpServers": {
"journal": {
"command": "python",
"args": ["/absolute/path/to/vibedna-journal-mcp/server.py"],
"env": { "JOURNAL_ROOTS": "/path/to/your/projects" }
}
}
}Then ask Claude: "Install the journal CLAUDE.md rule globally." That is the step that makes it read and write the journals on its own.
Cursor
Add the same mcpServers block to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project).
Claude Desktop
Add the same mcpServers block to claude_desktop_config.json (Settings > Developer > Edit Config), then restart Claude Desktop.
INSTALL.md is a step-by-step guide written so you can paste it into an AI chat and let the AI do the install.
Configuration
Variable | Default | What it does |
|
| Folders to scan for |
|
| Where the search index and optional config live |
|
|
|
Journal scaffold
journal_create starts every journal with these sections:
## Vision / Why this exists
## Current state
## Roadmap
## Decisions log
## Incidents
## Handoff for next session
## Recent entriesSecurity
See SECURITY.md for what the server reads, writes and sends.
License
MIT, see LICENSE. Copyright (c) 2026 VibeDNA.
Support: admin@vibedna.ai
This server cannot be deployed
Maintenance
Related MCP Connectors
Personal context for every AI: search, read, and write back to your private Markdown library.
Shared project memory that keeps teammates and AI agents aligned across sessions.
- OneLoreOAuthai.onelore
Shared project context for AI agents and teams: docs, tasks, and messages that stay current.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Related MCP Servers
- FlicenseBqualityDmaintenanceEnables AI assistants to automatically log and manage conversation history with developers in structured markdown format. Provides powerful search and context suggestions to help AI understand project history and maintain continuity across sessions.41-
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with persistent project memory to retain architectural decisions, code patterns, and domain knowledge across sessions. It stores data locally in a SQLite database, allowing agents to remember, recall, and manage project-specific context using full-text search.8 npmApache 2.0
- AlicenseNot gradedqualityBmaintenanceGives AI assistants persistent, queryable project memory for decisions, patterns, and rules, reducing the need to re-explain context in every prompt.11Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to read and write to a personal knowledge vault of markdown notes, projects, and tasks, with tooling for search, capture, daily logs, and project management across different AI tools.MIT