Fresh Jots MCP Server
This server lets you manage Fresh Jots notes and folders through any MCP-compatible AI client.
Notes
List notes: Retrieve summaries with optional filtering by folder/format, sort order, and pagination.
Read a note: Fetch full content by exact filename or numeric ID.
Create a note: Create a new plain-text note with a title, optional body, and optional folder.
Append to a note: Append text to a note by exact filename, automatically creating it if it doesn't exist — ideal for logs, AI session transcripts, or journals.
Update a note: Modify a plain-text note's title, body, and/or folder; only supplied fields are changed.
Delete a note: Permanently delete a note by numeric ID (append-only notes cannot be deleted).
Move a note: Move a note into a folder or remove it from any folder.
Folders
List folders: Retrieve all folders, ordered alphabetically.
Create a folder: Create a new uniquely named folder.
Rename a folder: Rename an existing folder by numeric ID.
Delete a folder: Delete a folder by numeric ID; its notes are un-filed but not deleted.
Key limitation: Only plain-text notes can be created or edited; rich (Trix) notes can only be listed and read.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
freshjots-mcp
A Model Context Protocol (MCP) server for Fresh Jots. It exposes your Fresh Jots notes as MCP tools, so any MCP client — Claude Desktop, Claude Code, Cursor, and others — can read and write them directly. Point your AI agent's output at a Fresh Jots note, log your coding sessions, or let an assistant search and update your notebook, all through the API.
MCP is an open standard for connecting AI assistants to external tools and data — think of it as a universal adapter, so one integration works across every compatible client.
What you can do
The server talks to the Fresh Jots REST API over a bearer token and exposes these tools:
Notes — list_notes, read_note, create_note, append_to_note, update_note, delete_note, move_note
Folders — list_folders, create_folder, rename_folder, delete_folder
The standout is append_to_note: it appends to a note addressed by an exact filename (e.g. ai-sessions.txt) and creates the note on first write. Call it repeatedly to accumulate a log — AI session transcripts, cron output, a running journal — in one place.
Notes are plain text through the API: rich (Trix) notes can be listed and read, but only plain notes can be created or edited here.
Related MCP server: aws-helper MCP Server
Requirements
Node.js 18 or newer
A Fresh Jots API token (Dev or Team plan). Create one at https://freshjots.com/settings/api_tokens. Tokens look like
mn_….
Install
Until this is published to npm, build it from source:
git clone https://github.com/Goran-Arsov/freshjots-mcp.git
cd freshjots-mcp
npm install # also builds via the prepare script
npm run build # or build explicitlyThe runnable server is then dist/index.js.
Configuration
The server reads its token from the environment:
FRESHJOTS_TOKEN(required) — yourmn_…API token.FRESHJOTS_API_TOKENis also accepted.FRESHJOTS_BASE_URL(optional) — defaults tohttps://freshjots.com/api/v1. Override for a self-hosted or staging instance.FRESHJOTS_PASSPHRASE(optional) — enables transparent client-side encryption (see below).
Encryption
Set FRESHJOTS_PASSPHRASE and the server can keep notes Fresh Jots cannot read. create_note and append_to_note take an encrypt: true argument that encrypts the body locally before it ever leaves your machine, and marks the note client-encrypted; read_note takes decrypt: true to decrypt it back. The model works in plaintext while Fresh Jots stores only ciphertext — you hold the only key, so lose the passphrase and the note is unrecoverable. Encryption is per-note and personal-only (not team notes); a note's title and metadata stay in the clear. The format (fj1: AES-256-CBC + HMAC-SHA256, PBKDF2) is interoperable with the JS, Python, Ruby, and shell clients. See https://freshjots.com/encrypted-notes.
Claude Desktop
Add to claude_desktop_config.json (Settings → Developer → Edit Config):
{
"mcpServers": {
"freshjots": {
"command": "node",
"args": ["/absolute/path/to/freshjots-mcp/dist/index.js"],
"env": { "FRESHJOTS_TOKEN": "mn_your_token_here" }
}
}
}Claude Code
claude mcp add freshjots --scope user \
-e FRESHJOTS_TOKEN='${FRESHJOTS_TOKEN}' \
-- node /absolute/path/to/freshjots-mcp/dist/index.jsUsing '${FRESHJOTS_TOKEN}' (single-quoted) stores the reference, not the secret — Claude Code expands it from your shell environment at launch, so keep export FRESHJOTS_TOKEN=mn_… in your shell profile. Or pass the literal token with -e FRESHJOTS_TOKEN=mn_… if you prefer it in the config.
Cursor
Add to ~/.cursor/mcp.json (or a project .cursor/mcp.json):
{
"mcpServers": {
"freshjots": {
"command": "node",
"args": ["/absolute/path/to/freshjots-mcp/dist/index.js"],
"env": { "FRESHJOTS_TOKEN": "mn_your_token_here" }
}
}
}Once published to npm, command: "npx", args: ["-y", "freshjots-mcp"] will replace the local path in any of the above.
Development
npm run build # compile TypeScript to dist/
npm test # unit tests (fetch stubbed; no network)
node smoke.mjs # live end-to-end test against the real API — needs FRESHJOTS_TOKEN;
# creates only clearly-marked [mcp-test] notes/folders and deletes themLicense
MIT © Goran Arsov
Available Tools
11 toolsappend_to_noteAppend to a note (creates it if missing)AInspect
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.
Inputs: filename (required), text (required), append_only.
create_folderCreate a folderAInspect
Create a new folder. Folder names are unique (case-insensitive) within the account.
Inputs: name (required).
create_noteCreate a noteAInspect
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.
Inputs: title (required), body, folder_id.
delete_folderDelete a folderADestructiveInspect
Delete a folder by its numeric id. Notes inside it are NOT deleted — they are moved out of the folder (un-filed).
Inputs: id (required).
delete_noteDelete a noteADestructiveInspect
Delete a note by its numeric id. Append-only notes cannot be deleted via the API. This cannot be undone through this server.
Inputs: id (required).
list_foldersList foldersARead-onlyInspect
List all folders in the account (id, name, timestamps), ordered alphabetically.
Inputs: no named parameters.
list_notesList notesARead-onlyInspect
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.
Inputs: limit, offset, format, folder_id, +1 more.
move_noteMove a note to a folderAInspect
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.
Inputs: id (required), folder_id (required).
read_noteRead a noteARead-onlyInspect
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.
Inputs: filename, id.
rename_folderRename a folderBInspect
Rename an existing folder, addressed by its numeric id.
Inputs: id (required), name (required).
update_noteUpdate a noteAInspect
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.
Inputs: filename, id, title, body, +1 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Google Keep-style notes app with an MCP server for AI agents to read/write notes.
An MCP server that used to create notes
Shared rooms and durable notes for agents over plain HTTP: rendezvous, hand-off, coordination.
Related MCP Servers
- AlicenseBqualityDmaintenanceA simple MCP server that recalls and saves memories from and to Apple Notes.213MIT
- AlicenseCqualityDmaintenanceA Model Context Protocol server that implements a simple notes system, allowing users to create, list, and summarize text notes.37 npmISC
- FlicenseNot gradedqualityDmaintenancePersonal note management server that enables creating, reading, updating, deleting, listing, and searching notes with support for titles, content, and tags.-
- AlicenseAqualityDmaintenanceComprehensive Apple Notes MCP server for local macOS note management.144,261 npmMIT