MCP servers that ship as code — a repository or a package you install and run locally (usually over stdio). They have no hosted endpoint, so we cannot probe or grade them: instead each one shows its repository, install command, license, stars and when it was last updated.
Collected from GitHub repositories and npm, PyPI, Cargo, Go, Maven, NuGet and RubyGems packages tagged as MCP servers, the official MCP Registry, Docker's MCP catalog, ModelScope, Baidu MCP World, Cline and other public directories; one entry per repository. A server that also offers a hosted endpoint is listed under Remote instead. These entries are not counted in our reachability, verification or readiness statistics.
-
atomnoteactive
Atomic notes: typed, schema-checked markdown atoms; the note command and its MCP tools. Name reserved; the tool follows.
npm -
jobs-tools-knowledgebaseupdated this year
MongoDB Atlas-based Zettelkasten knowledge management via MCP - Unified knowledge base with atomic notes, tag-based linking, and lifecycle management
npm MIT -
A Model Context Protocol (MCP) server that implements the Zettelkasten knowledge management methodology, allowing you to create, link, explore and synthesize atomic notes through Claude and other MCP-compatible clients.
go MIT ★ 168 -
An OpenClaw (2026.4/2026.6+) and Hermes Agent plugin that turns AI conversations into a permanent Zettelkasten knowledge base — atomic notes, bi-directional links, knowledge distillation, and MCP tool exposure.
MIT ★ 17 -
Local-first Obsidian memory for Hermes Agent: bounded automatic recall, CJK lexical search, atomic MCP note tools
MIT -
agentedgithub.com/frane/agentedno update data
A text editor for LLMs, not humans. Take ed, the line editor that nobody has voluntarily used since about 1975, and rebuild it for an environment where the typing user is a language model. Short verbs, line addresses, no modes, no TUI. What an editor optimises for changes when the user is the model: round trips per task, tokens per command, an editing buffer with a long memory, and an undo tree that remembers the branches the agent abandoned, because that's often where the interesting work was. ## Features - **Fewer round trips.** Read-before-Edit is unnecessary; on conflict the response carries the new content so you reconcile in one call instead of pre-reading every time. - **Branching undo.** Walked-back work stays addressable instead of being thrown away when you pick a different path. - **Three-way merge.** Concurrent agents get a structured conflict response instead of a silent overwrite. - **Atomic batches.** Multi-file refactors run all-or-nothing instead of leaving half-applied state on failure. - **Cross-file moves and regex replace as primitives.** Operations the built-in tools can't express cleanly become single calls. - **Drift detection.** External edits to an open file are folded into the tree instead of being clobbered by the next write. - **Inline diagnostics.** Type errors and lint findings surface on save, not at the next build many edits later. - **Cross-session memory.** Per-file notes persist between sessions and surface inline on the next open. - **Audit log.** Every operation recorded with actor and timestamp, so two agents in one workspace can't argue about who moved the head. ## Multi-workspace (v0.4.0) One MCP server registration handles every project you mention. Tool calls route to the workspace owning the absolute path you pass; each project gets its own SQLite, its own undo tree, its own LSP daemon — lazily spawned on first touch. Desktop hosts (Claude Desktop, Codex Desktop, Cursor) install the server once globally and use it across projects without per-project config. ## Install `ae` must be installed locally; this MCP bundle registers `ae serve` as a stdio server. ```sh brew tap frane/tap && brew install agented # or curl -sSL https://raw.githubusercontent.com/frane/agented/master/install.sh | sh ``` Pure Go, single static binary, Apache 2.0. Source: https://github.com/frane/agented
smithery -
MCP server exposing a single Markdown+YAML vault to AI agents with structure-aware tools: outline reads, section-level edits, frontmatter properties, atomic multi-file transactions, and git sync.
★ 1