Skip to main content
An agent can reach KiwiFS through a mounted filesystem, the REST API, MCP, or a plain llms.txt index. Every route lands on the same files, and every write goes through the same pipeline, so the choice is about what your agent’s environment supports.

Filesystem

With a local folder or a mount (NFS, FUSE, WebDAV, or S3), the agent uses commands it already knows. No SDK, driver, or custom protocol.
Terminal
Writes made directly on disk are picked up by the file watcher, then committed and indexed like any other write.

REST API

Terminal
See the API overview for every endpoint.

MCP

MCP is the most structured interface: 78 tools covering files, search, DQL, drafts, refactoring, memory, workflows, task claims, graph analytics, imports, and more.
Terminal
A running kiwifs serve also exposes MCP at /mcp. Agents should call kiwi_context first to load the schema, playbook, index, and rules. See MCP for client setup and the full tool reference.

llms.txt

GET /llms.txt lists every page grouped by folder with links, following the llms.txt convention. GET /llms-full.txt returns every page’s markdown in one response, truncated with a notice past a size cap. When auth is enabled, both list only public or published pages.

One pipeline for every protocol

Setup for each: Alternate protocols.

Attribution and provenance

Tell KiwiFS who is writing and why. Both work on any write. The type:id format is required; a malformed value is ignored. Later, find everything a run produced:
Terminal
Use the ETag from a read as If-Match (REST) or if_match (MCP) on the next write. If another agent changed the page in between, your write fails with a conflict instead of overwriting their edit.

MCP

Client setup and all 78 tools.

Agent playbook

The files that onboard an agent to a knowledge base.

Alternate protocols

NFS, S3, WebDAV, and FUSE setup.

Task claims

Keep agents from editing the same page at once.
Last modified on October 19, 2026