Give an agent scoped read and write access to local knowledge-base directories.

Capabilities

What it actually does.

• Read, write, list and delete notes across every declared base.
• Create folders and rename entries, so the agent can restructure rather than only edit.
• Report which aliases are declared and what each one resolves to, so the agent can discover its own boundaries.
• Name the base on every call, which is what lets one registration serve many knowledge bases at once.

State

How finished it is.

Public source, not published to any package registry. Clone it, build it, and register the built server with your MCP client. The path validation and the alias model are the settled parts; the tool surface is deliberately small.

Boundaries

What it deliberately does not do.

Every path is validated twice, lexically and then through realpath, so neither a traversal nor a symlink reaches outside the declared root and no call under one alias wanders into a sibling base. Dotfiles and repository metadata stay hidden from ordinary tools. It makes no network request and performs no authentication: it reads and writes notes, and holds no knowledge of its own.

Authority

What this repository owns.

The knowledge-base filesystem adapter. It reads and writes notes; it holds no knowledge of its own.

That boundary is deliberate. The ecosystem separates philosophy, engineering discipline, capability semantics, portable standards, and executable behaviour so that none of them can quietly absorb another. The full directory shows where this project sits relative to the rest.