MCP Journaling Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JOURNAL_DIR | No | Directory for saving journal files | ~/Documents/journal |
| FILE_EXTENSION | No | Journal file extension | .md |
| FILENAME_PREFIX | No | Prefix for file names | journal |
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 |
|---|---|
| start_new_sessionA | Start a new journaling session by clearing previous conversation log. Returns: str: Welcome message with current save location |
| record_interactionB | Record both the user's message and assistant's response. Args: user_message: The user's message assistant_message: The assistant's response Returns: str: Confirmation message |
| generate_session_summaryC | Generate a markdown summary of the journaling session. Args: summary: The llm generated summay of the conversation Returns: str: Confirmation message |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| start_journaling | Interactive prompt to begin a journaling session. Returns: Starting prompt for journaling session |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| journals://recent |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: start_new_session initiates a session, record_interaction logs individual exchanges, and generate_session_summary creates a final summary. The actions (start, record, generate) and targets (session, interaction, summary) are unambiguous.
All tools follow a consistent verb_noun pattern with snake_case: start_new_session, record_interaction, and generate_session_summary. The naming is predictable and readable across the set.
Three tools are reasonable for a journaling server, covering core operations (start, record, summarize). It might feel slightly thin if advanced features like editing or searching past entries are needed, but it's well-scoped for basic functionality.
The tools cover the essential lifecycle of a journaling session: starting, recording interactions, and summarizing. Minor gaps exist, such as no tools for retrieving or managing past sessions, but agents can work around this with the provided operations.