Local MCP server for LiveJournal journals. It uses the legacy LiveJournal XML-RPC API to read entries, read comments, post to your own journal, and build a local SQLite cache for search.
Livejournal is an MCP project maintained in the pavelber/livejournal-mcp repository. The maintainer describes its purpose as “Local MCP server for LiveJournal journals. It uses the legacy LiveJournal XML-RPC API to read entries, read comments, post to your own journal, and build…”. Read the project documentation for the complete scope.
The project provides a local client configuration using C:\path\to\livejournal-mcp\.venv\Scripts\python.exe. Follow the repository’s build and installation steps before copying it, and replace example paths with the paths on your own computer.
The example declares LJ_USERNAME, LJ_PASSWORD, LJ_JOURNAL, LJ_CACHE_PATH. Secret-looking values have been replaced with placeholders. Required and optional labels are shown only when the documentation states them.
Project documentation · Repository · Discovery listing. This profile records the public documentation checked on 2026-10-08.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| check_login | list_entries |
| get_entries_for_date | search_recent_entries |
| get_entry | sync_entries |
| get_entry_comments | create_post |
| generate_session | cache_recent_entries |
| cache_entries_for_date | cache_synced_entries |
| cache_entry | search_cached_entries |
| list_cached_entries | get_cached_entry |
| cache_stats | clear_cache |
{
"mcpServers": {
"livejournal": {
"command": "C:\\path\\to\\livejournal-mcp\\.venv\\Scripts\\python.exe",
"args": [
"-m",
"livejournal_mcp.server"
],
"env": {
"LJ_USERNAME": "your_livejournal_username",
"LJ_PASSWORD": "YOUR_LJ_PASSWORD",
"LJ_JOURNAL": "your_livejournal_username",
"LJ_CACHE_PATH": "C:\\Users\\you\\AppData\\Local\\livejournal-mcp\\livejournal.sqlite3"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| LJ_USERNAME | Declared in the maintainer’s client configuration. | Check documentation |
| LJ_PASSWORD | Declared in the maintainer’s client configuration. | Check documentation |
| LJ_JOURNAL | Declared in the maintainer’s client configuration. | Check documentation |
| LJ_CACHE_PATH | Declared in the maintainer’s client configuration. | Check documentation |
Inspect PostgreSQL schemas and run read-only queries with the archived MCP reference server. Review its maintenance status before choosing it.
Connect the Notion MCP server to search workspace content and work with pages and databases through Notion’s hosted OAuth service.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Query, modify and analyse local SQLite databases in conversation — the fastest way to chat with a data file.
Metabase ships its own MCP endpoint — search your BI content, build and run queries, and save questions and dashboards without leaving the chat.
Official MongoDB server covering data, schemas and Atlas management — from find queries to spinning up clusters.