Mcp Standardnotes

io.github.lozitPublished by GitHub account lozitv0.6.0Updated Oct 24, 2026

End-to-end encrypted access to a Standard Notes vault (protocol 004, local stdio only).

VerifiedSTDIODesktop onlyProductivity & Workflow Files & Storage

Server details

Identifier: io.github.lozit/mcp-standardnotes
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account lozit for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.lozit%2Fmcp-standardnotes.svg)](https://sourceweft.com/mcp/io.github.lozit%2Fmcp-standardnotes?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets an assistant read, search, create, update, and delete notes and tags in an end-to-end encrypted Standard Notes vault from the local machine.

What you can do: Provides tools for browsing and searching notes (notes_list, notes_search, notes_get), writing them (notes_create, notes_update, notes_delete, notes_create_many for batches up to 50), and viewing vault statistics. It also offers full tag management (tags_list, tags_get, tags_create, tags_update, tags_delete, tags_attach, tags_detach) and a sync tool to force a server sync. Decryption happens locally, and the server communicates over stdio only.
When to use it: Useful when you keep notes in Standard Notes and want an assistant to summarize, draft, organize, or search them without exporting the vault. It suits users who want local-only access to an encrypted vault rather than a cloud intermediary.
Requirements: Node.js 20 or newer, a Standard Notes account on protocol 004, and an OS keychain (macOS Keychain, Linux libsecret, or Windows Credential Vault). Run npx mcp-standardnotes-login once to enter the password and store the session; set SN_EMAIL, and optionally SN_SERVER_URL and SN_CERT_FINGERPRINT for self-hosted servers. Transport is stdio, desktop only.

Before you install

The server can create, update, and delete notes and tags, so assistant mistakes can alter or remove vault content. It handles the account password and master key; the password is prompted at login and the session is stored in the OS keychain. SN_EMAIL is required, and SN_CERT_FINGERPRINT is optional for self-hosted TLS pinning. It is an unofficial third-party integration, not affiliated with Standard Notes Ltd.

Installation

In SourceWeft

Open Mcp Standardnotes in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[mcp-standardnotes]

mcp-standardnotes

[CI] [License: MIT] [Node: ≥20]

Give Claude secure read/write access to your Standard Notes vault — end-to-end encrypted, local stdio only, zero cloud middleman.

Ask Claude to summarize your notes, draft new ones, organize tags, search across your vault — all while your master key stays on your machine. Works with Claude Code, Claude Desktop, and any MCP-compatible client.

Disclaimer. This is an unofficial third-party integration. Not affiliated with, endorsed by, or sponsored by Standard Notes Ltd. "Standard Notes" is a trademark of Standard Notes Ltd.

Why

🔒 End-to-end encrypted. All decryption happens locally using audited libsodium primitives (Argon2id + XChaCha20-Poly1305 IETF). Your password never leaves RAM; your master key never leaves your machine.
🔌 Local stdio only. No network port is ever opened by this server.
🔑 OS keychain for session storage. macOS Keychain, Linux libsecret, Windows Credential Vault — never plaintext files.
☁️ Works with the official cloud or self-hosted Standard Notes servers.

Features

Tool	What it does
`notes_list` / `notes_search` / `notes_get`	Browse and search your notes (filter by tag with `tag: "<uuid-or-title>"`)
`notes_create` / `notes_update` / `notes_delete`	Write notes (markdown, super, code, rich-text, task, spreadsheet, plain-text)
`notes_create_many`	Batch-create up to 50 notes in one sync push
`notes_stats`	Vault stats: counts, sizes, oldest/newest/largest note
`tags_list` / `tags_get` / `tags_create` / `tags_update` / `tags_delete`	Full tag CRUD
`tags_attach` / `tags_detach`	Link/unlink tags to notes
`sync`	Force a sync with the server

notes_create and notes_update accept an optional tags: string[] (tag UUIDs) to link tags at write time.

Requirements

Node.js ≥ 20
A Standard Notes account on protocol 004 (default for any account created or upgraded since 2020)
macOS, Linux, or Windows with a working OS keychain

Quickstart

1. Install

Or run from a clone if you prefer:

bash

git clone https://github.com/lozit/mcp-standardnotes.gitcd mcp-standardnotesnpm install && npm run build

git clone https://github.com/lozit/mcp-standardnotes.gitcd mcp-standardnotesnpm install && npm run build

2. Log in once

You'll be prompted for email and password. The password derives your master key in memory (Argon2id) and is never written to disk. An encrypted session is stored in your OS keychain; subsequent runs reuse it automatically. At the end of login, you're offered to wire the server into Claude Desktop in one step — accept it, restart Desktop, done.

3. Hook it up to Claude

Claude Desktop (macOS / Windows) — easiest path, run:

This writes the right entry (absolute Node + binary paths, your email from the keychain) into ~/Library/Application Support/Claude/claude_desktop_config.json (or %APPDATA%/Claude/claude_desktop_config.json on Windows), backing up any existing config first. Quit Claude Desktop fully (⌘Q) and relaunch.

Claude Code — let the claude CLI do it:

Or add to ~/.claude.json / .mcp.json manually:

json

{  "mcpServers": {    "mcp-standardnotes": {      "type": "stdio",      "command": "mcp-standardnotes",      "env": { "SN_EMAIL": "[email protected]" }    }  }}

{  "mcpServers": {    "mcp-standardnotes": {      "type": "stdio",      "command": "mcp-standardnotes",      "env": { "SN_EMAIL": "[email protected]" }    }  }}

Then /mcp to reconnect.

Any other MCP client — run node dist/index.js with SN_EMAIL set in the environment. Transport is stdio.

Self-hosting Standard Notes? See docs/self-hosted.md for the docker-compose recipe and how to pin your TLS certificate.

Want a remote agent (Hermes on a VPS, self-hosted LangGraph, etc.) to use your vault? See docs/remote-agent-bridge.md for the full Cloudflare Tunnel + MCP Portals setup. Your master key stays on your Mac; the agent talks to a public HTTPS endpoint gated by a Cloudflare service token, and Portals handles automatic MCP tool discovery, multi-server bundling, and Access application generation.

Configuration

Variable	Default	Description
`SN_EMAIL`	required	Your SN account email. Must match what you used with `npm run login`.
`SN_SERVER_URL`	`https://api.standardnotes.com`	Sync server URL. Change for self-hosted instances.
`KEYCHAIN_SERVICE`	`mcp-standardnotes`	Override the keychain service name (useful for multiple accounts).
`SN_CERT_FINGERPRINT`	unset	SHA-256 TLS cert pin for self-hosted servers (64 hex chars, colons optional). See docs/self-hosted.md.

Security at a glance

Password in RAM only during key derivation. Never logged, never stored.
Session + master key hex → OS keychain only. Never plaintext files.
stdio transport only. No HTTP port, ever.
All logs go to stderr, routed through a redactor that masks passwords, keys, JWTs, and token-like strings.
All tool inputs validated by zod.
npm audit HIGH/CRITICAL is a merge blocker in CI.
Only the protocol 004 framing is implemented locally; all cryptographic primitives come from libsodium-wrappers-sumo.

Full threat model and deep-dive: docs/protocol-004.md. Security policy, vulnerability reporting, and dependency-advisory notes: SECURITY.md.

Troubleshooting

Common issues and fixes: docs/troubleshooting.md.

Logout

Roadmap

Upcoming work tracked in ROADMAP.md.

Contributing

Contributions welcome. See CONTRIBUTING.md for setup, tests, and PR checklist.

License

MIT — use it, fork it, ship it.

Credits

Standard Notes for the encryption design and public API.
Model Context Protocol and Anthropic for the MCP SDK.
libsodium by Frank Denis, exposed via libsodium-wrappers-sumo.

Source: README.md at commit 749d466

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.6.0LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts