Chrismbryant Claude Journal Mcp
chrismbryant-claude-journal-mcp is a Claude Code plugin for the Operate phase that provides lightweight journal memory via slash commands, skills, and auto-capture hooks with no ML dependencies.
by chrismbryant · github.com/chrismbryant/claude-journal-mcp
Add chrismbryant’s journal/memory plugin so Claude Code captures session context, exposes slash commands, and recalls decisions without heavyweight ML infra.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install chrismbryant-claude-journal-mcp@chrismbryant/claude-journal-mcpBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:chrismbryant/claude-journal-mcp") and the paste-ready config with skillselion.get_install_config("plugin:chrismbryant/claude-journal-mcp").
What it does
chrismbryant-claude-journal-mcp is a Claude Code plugin that gives solo builders a lightweight journal and memory layer without standing up ML pipelines. It combines slash commands, proactive skills, and auto-capture hooks so decisions, blockers, and session notes survive between chats—critical when one person context-switches across idea, build, ship, and operate work. Install it while configuring agent tooling, then rely on it journey-wide whenever you need Claude to remember what you already decided instead of re-explaining the product. The design prioritizes simplicity and local-feeling persistence over semantic search appliances, which keeps setup approachable for beginners yet valuable for advanced users running long arcs. Confidence is solid on the stated feature set from the catalog description, though deep hook configuration details live in the upstream repo.
Highlights
- Lightweight journal and memory plugin for Claude Code with zero ML dependencies.
- Slash commands plus proactive skills for quick capture and recall during coding sessions.
- Auto-capture hooks that persist notable context without manual copy-paste.
- Single-plugin bundle (chrismbryant/claude-journal-mcp) aimed at solo continuity across projects.
- Fits agent-tooling setup during build and long-running memory needs during operate.
Why builders use it
Solo builders lose thread across Claude Code sessions because context lives only in chat history, forcing repeated explanations and inconsistent decisions.
After install, hooks and journal commands persist session memory locally so Claude can proactively reuse notes and you iterate faster without external ML services.
At a glance
- Type - Plugin in Productivity.
- Adoption - 0 installs, 5 stars, 0 votes.
FAQ
Who is chrismbryant-claude-journal-mcp for?
It is for Claude Code users who want lightweight session memory, slash commands, and auto-capture without installing ML-heavy memory stacks.
When should I use chrismbryant-claude-journal-mcp?
Use it whenever you work in Claude Code across days or weeks—during build setup and continuously while operating and iterating on the product.
How do I add chrismbryant-claude-journal-mcp to my agent?
Install the chrismbryant/claude-journal-mcp plugin in Claude Code, enable its hooks per the repo README, and use the provided slash commands or skills to capture and query journal entries.
Comments
Share how you use chrismbryant-claude-journal-mcp, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.