static-md-e2e
OfficialRelated Servers
Alternatives to static-md-e2e
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server for AI agents to read, write, and organize notes in a local-first, human-in-the-loop note-taking app.3 npm2MIT
- AlicenseAqualityCmaintenanceMCP server for managing a local, domain-agnostic knowledge base using Markdown notes with frontmatter. Enables AI agents to capture, read, search, link, and maintain notes with atomic writes and privacy controls.13MIT
- AlicenseNot gradedqualityCmaintenanceA local-first MCP server that gives AI assistants long-term memory by storing, searching, and recalling notes as Markdown files on your machine.9 npmMIT
- AlicenseNot gradedqualityBmaintenanceA self-hosted MCP server that gives AI coding agents shared live docs, memory and session context from plain Markdown files on disk, with search, note editing, hand-over tasks and linting. It also provides a web UI with a graph of how notes connect, password-protected tokens, and offline sync.MIT
- AlicenseAqualityCmaintenanceAn MCP server that gives AI models a persistent notebook backed by a folder of Markdown files, with tools to discover, read, write, edit, and delete notes.9MIT
- AlicenseNot gradedqualityBmaintenanceA local MCP server that lets compatible clients read, search, and edit notes in an Obsidian vault, with path restrictions to the configured vault root and formatting-preserving frontmatter updates.MIT
TDQS
Scored across 3 tools
Each tool maps to a single distinct CRUD action on the same resource (encrypted note), with clear boundaries between reading, creating, and updating. There is no plausible way to confuse them, and the mode parameter on update is scoped to that tool only.
All three names follow a strict verb_noun pattern with a shared, stable noun phrase: read_encrypted_note, create_encrypted_note, update_encrypted_note. Predictable and easy to guess the missing operations from.
Three tools is on the thin side, but each is substantial and covers a distinct lifecycle stage, so nothing feels redundant. A slight under-provisioning is the only issue.
The domain is note management, and the surface covers create, read, and update, but there is no delete/remove tool and no way to list or discover the user's notes or folders — agents cannot enumerate notes without an out-of-band link. These are notable gaps for a full note lifecycle.