Obsidian Diary MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DIARY_PATH | Yes | Required path to your diary directory | |
| MAX_THEMES | No | Max themes per analysis | 15 |
| MIN_THEME_FREQUENCY | No | Min word frequency for themes | 1 |
| RECENT_ENTRIES_COUNT | No | How many recent entries to analyze | 3 |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_diary_templateB | Create a new diary entry template with reflection prompts based on recent entries. Args: date: Date for the entry in YYYY-MM-DD format. If not provided, uses today's date. Returns: A formatted diary template with reflection prompts |
| save_diary_entryB | Save a diary entry and automatically add relevant backlinks. Args: date: Date for the entry in YYYY-MM-DD format content: The diary entry content Returns: Success message with the file path and auto-generated backlinks |
| read_diary_entryB | Read an existing diary entry. Args: date: Date of the entry in YYYY-MM-DD format Returns: The diary entry content |
| list_recent_entriesB | List recent diary entries. Args: count: Number of recent entries to list (default: 10) Returns: A list of recent entry dates |
| update_entry_backlinksB | Update the backlinks for an existing diary entry based on its current content. Args: date: Date of the entry in YYYY-MM-DD format Returns: Success message with updated backlinks |
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 5 tools
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.
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.
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.
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.