Fresh Jots MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FRESHJOTS_TOKEN | No | Your Fresh Jots API token (mn_...). Alternatively, use FRESHJOTS_API_TOKEN. | |
| FRESHJOTS_BASE_URL | No | Base URL for the Fresh Jots API. Override for self-hosted or staging instances. | https://freshjots.com/api/v1 |
| FRESHJOTS_API_TOKEN | No | Alternative name for the Fresh Jots API token. |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesA | List the account's notes (most-recently-updated first by default) as summaries: id, filename, title, format, timestamps, and a body excerpt. Filter by folder or format. Both plain and rich notes are listed, but only plain notes can be created or edited through this server. |
| read_noteA | Read a single note in full (including its complete plain_body) by exact filename (e.g. "ai-sessions.txt") or numeric id. Provide exactly one of filename or id. |
| create_noteA | Create a new plain-text note. The server derives the filename from the title. To create a note you can address later by an exact filename of your choosing, use append_to_note instead (it creates the note on first write). Plain text only. |
| append_to_noteA | Append text to the note with the given exact filename, creating the note if it does not exist yet (find-or-create). This is the primitive for logging: call it repeatedly to accumulate entries (AI session logs, cron output, journal lines) in one note addressed by a stable filename like "ai-sessions.txt". Plain text only. |
| update_noteA | Update a plain-text note's title, body, and/or folder, addressed by exact filename or numeric id. Only the fields you supply change; omitted fields are left untouched. Rich-format and append-only notes reject body/title edits. Provide exactly one of filename or id. |
| delete_noteA | Delete a note by its numeric id. Append-only notes cannot be deleted via the API. This cannot be undone through this server. |
| move_noteA | Move a note (by numeric id) into a folder, or out of any folder. Pass a folder_id to file it there, or null to un-file it. |
| list_foldersA | List all folders in the account (id, name, timestamps), ordered alphabetically. |
| create_folderA | Create a new folder. Folder names are unique (case-insensitive) within the account. |
| rename_folderB | Rename an existing folder, addressed by its numeric id. |
| delete_folderA | Delete a folder by its numeric id. Notes inside it are NOT deleted — they are moved out of the folder (un-filed). |
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 11 tools
Each tool has a distinct purpose: create vs append for notes, CRUD for folders and notes are clearly separated. No two tools are ambiguous.
All tools follow a consistent verb_noun pattern with snake_case (e.g., create_note, delete_folder, list_notes). No deviations.
11 tools cover a complete CRUD surface for notes and folders, with additional operations like append and move. The count is well-scoped for the domain.
The tool set covers basic note and folder lifecycle. Minor gap: no explicit search or folder content retrieval, but list_notes with folder filtering mitigates this.