Skip to main content
Glama
madebygps

Obsidian Diary MCP Server

by madebygps
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Obsidian Diary MCP Server

No user-submitted related servers found.

    Related Servers

    • Obsidian Palace MCP

      Probably-Computers
      A
      license
      Not graded
      quality
      F
      maintenance
      Turns your Obsidian vault into an AI memory palace, enabling AI assistants to store knowledge with intent-based organization, retrieve information through full-text search, auto-link related notes, and query using Dataview syntax while maintaining provenance tracking.
      4 npm
      AGPL 3.0

    • Dear Agent

      BitmapAsset
      A
      license
      A
      quality
      C
      maintenance
      Automatically maintains a personal journal on behalf of an AI agent, storing text, photos, and voice notes as plain markdown files locally. Enables agents to add entries, recall memories, and reflect on patterns without user intervention.
      11
      52 npm
      MIT

    • MegaMem

      C-Bjorn
      A
      license
      Not graded
      quality
      A
      maintenance
      Syncs Obsidian notes into a temporal knowledge graph and exposes 23 MCP tools for AI assistants to read, search, and write to your vault, enabling persistent memory across conversations.
      79
      MIT
    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

    A3.7/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: create_diary_template generates templates, list_recent_entries lists entries, read_diary_entry reads content, save_diary_entry saves new entries, and update_entry_backlinks updates backlinks. The descriptions reinforce these distinct functions, making misselection unlikely.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with clear, descriptive names (e.g., create_diary_template, list_recent_entries). There are no deviations in naming style, making the set predictable and easy to understand at a glance.

    Tool Count5/5

    With 5 tools, this server is well-scoped for a diary management system. Each tool serves a specific, necessary function (CRUD operations and backlink management) without redundancy, making the count appropriate for the domain's scope.

    Completeness4/5

    The toolset covers core diary operations well: create (via save_diary_entry), read (read_diary_entry), list (list_recent_entries), and update (update_entry_backlinks), plus template creation. A minor gap is the lack of a delete tool, but agents can work around this, and the surface supports essential workflows without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources