Private Journal MCP Server

Created By
obraa year ago
A lightweight MCP server that provides Claude with a private journaling capability to process feelings and thoughts
Overview

What is Private Journal MCP?

Private Journal MCP is a lightweight Model Context Protocol (MCP) server designed to provide Claude with a private journaling capability, allowing users to process their thoughts and feelings effectively.

How to use Private Journal MCP?

To use Private Journal MCP, install it via npm and run the command private-journal-mcp to create journal entries in the .private-journal/ directory. You can also specify a custom journal path using the --journal-path option.

Key features of Private Journal MCP?

  • Multi-section journaling for different categories (feelings, project notes, etc.)
  • Semantic search capabilities using local AI embeddings
  • Completely private processing with no data leaving the machine
  • Timestamped entries with YAML frontmatter for structured metadata

Use cases of Private Journal MCP?

  1. Documenting personal feelings and emotional processing.
  2. Keeping track of project-specific notes and insights.
  3. Searching through journal entries using natural language queries.

FAQ from Private Journal MCP?

  • Is my data safe with Private Journal MCP?

Yes! All processing is done locally, ensuring complete privacy.

  • Can I customize the journal path?

Yes! You can specify a custom path using the --journal-path option.

  • What kind of entries can I create?

You can create entries for feelings, project notes, technical insights, and more.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
obra
Star
2
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago