Skip to main content
Glama
pavelber

LiveJournal MCP Server

by pavelber
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to LiveJournal MCP Server

No user-submitted related servers found.

    Related Servers

    • Opyt

      maimond123
      A
      license
      A
      quality
      B
      maintenance
      Enables AI clients to search, read, and analyze a local SQLite knowledge base built from the full public archives of people you follow, bookmark, or subscribe to, with tools for onboarding, querying, and topic tracking.
      12
      8
      MIT

    • Day One MCP Server

      benlen10
      F
      license
      Not graded
      quality
      D
      maintenance
      Read-only MCP server for Day One journal on macOS, enabling search and browsing of entries, photos, and metadata.
      2
      -

    • Amplenote Cache MCP Server

      mikekwright
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides access to your Amplenote SQLite database cache, enabling search and retrieval of notes and tasks, including full-text search, bidirectional references, task filtering by priority and due dates, and recently modified content tracking.
      -

    • ppdiary

      ppworks
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI-assisted diary management through natural language, allowing you to create, read, update, delete, and search diary entries stored locally in SQLite.
      -

    • mcp-feed-reader-crunchtools

      crunchtools
      A
      license
      B
      quality
      A
      maintenance
      Secure MCP server for RSS/Atom feed reading with SQLite backend. Enables feed management, entry search, and OPML import/export.
      17
      AGPL 3.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3/5.0

    Scored across 18 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources