Skip to main content
Glama
Fresh Jots MCP Server

Fresh Jots MCP Server

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

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 explicitly

The runnable server is then dist/index.js.

Configuration

The server reads its token from the environment:

  • FRESHJOTS_TOKEN (required) — your mn_… API token. FRESHJOTS_API_TOKEN is also accepted.

  • FRESHJOTS_BASE_URL (optional) — defaults to https://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.js

Using '${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 them

License

MIT © Goran Arsov

Available Tools

11 tools
append_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 folderA
Destructive
Inspect

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 noteA
Destructive
Inspect

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 foldersA
Read-only
Inspect

List all folders in the account (id, name, timestamps), ordered alphabetically.

Inputs: no named parameters.

list_notesList notesA
Read-only
Inspect

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 noteA
Read-only
Inspect

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

    A4.2/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a distinct purpose: create vs append for notes, CRUD for folders and notes are clearly separated. No two tools are ambiguous.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with snake_case (e.g., create_note, delete_folder, list_notes). No deviations.

    Tool Count5/5

    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.

    Completeness4/5

    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

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers