LiveJournal MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LJ_JOURNAL | No | Target journal, defaults to LJ_USERNAME | |
| LJ_BASE_URL | No | LiveJournal base URL, defaults to https://www.livejournal.com | https://www.livejournal.com |
| LJ_PASSWORD | Yes | LiveJournal password | |
| LJ_USERNAME | Yes | LiveJournal username | |
| LJ_CACHE_PATH | No | SQLite cache path | |
| LJ_CLIENT_VERSION | No | Client version string, defaults to Cursor-MCP/0.1.0 | Cursor-MCP/0.1.0 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_loginA | Validate LiveJournal credentials and return account basics. |
| list_entriesC | Read recent entries from your LiveJournal journal. |
| get_entries_for_dateA | Read LiveJournal entries for one date in YYYY-MM-DD format. |
| search_recent_entriesD | Search the most recent LiveJournal entries fetched from the API. |
| get_entryC | Read one LiveJournal entry by itemid. |
| sync_entriesB | Read entries changed since a LiveJournal sync timestamp. |
| cache_recent_entriesC | Fetch recent LiveJournal entries and save them to the local SQLite cache. |
| cache_entries_for_dateC | Fetch one date of LiveJournal entries and save them to the local SQLite cache. |
| cache_synced_entriesC | Fetch entries changed since a sync timestamp and save them to the local SQLite cache. |
| cache_entryB | Fetch one LiveJournal entry by itemid and save it to the local SQLite cache. |
| search_cached_entriesC | Search entries already saved in the local SQLite cache. |
| list_cached_entriesC | List entries already saved in the local SQLite cache. |
| get_cached_entryC | Read one entry from the local SQLite cache by itemid. |
| cache_statsC | Return local SQLite cache statistics. |
| clear_cacheB | Clear cached LiveJournal entries. Pass journal to clear one journal, or omit it for the default journal. |
| get_entry_commentsC | Read comments for a LiveJournal entry using LJ.XMLRPC.getcomments. |
| create_postC | Post a new entry to your LiveJournal journal. Defaults to dry_run and private. |
| generate_sessionC | Generate an ljsession cookie for authenticated LiveJournal web endpoints. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 18 tools
Each tool has a clearly distinct purpose, with caching, reading, authentication, and posting separated. Overlapping functions like cache_entries_for_date, cache_recent_entries, and cache_synced_entries are differentiated by date, recency, or sync timestamp.
All tool names follow a consistent verb_noun pattern in snake_case, such as cache_entries_for_date, create_post, check_login, and list_entries. No mixing of conventions.
18 tools is slightly on the higher side but still reasonable for a LiveJournal server covering authentication, caching, reading, searching, and posting. Each tool has a clear role, though some consolidation might be possible.
The tool set covers reading (multiple variants), caching, authentication, and creating entries, but lacks update and delete operations for entries. This is a notable gap for full CRUD.