KiwiFS gives agents four ways to access knowledge, from the most native (filesystem) to the most structured (MCP).Documentation Index
Fetch the complete documentation index at: https://docs.kiwifs.com/llms.txt
Use this file to discover all available pages before exploring further.
Filesystem access
When your agent has a real filesystem mount (NFS, FUSE, or local):REST API
When a filesystem mount isn’t available:MCP (Model Context Protocol)
The most structured interface, designed for Claude, Cursor, and other AI tools:kiwi_read, kiwi_write, kiwi_search, kiwi_tree, kiwi_query_meta, kiwi_query, kiwi_view_refresh, kiwi_delete, kiwi_rename, kiwi_bulk_write, kiwi_aggregate, kiwi_import, kiwi_export, kiwi_changes, kiwi_append, kiwi_search_semantic, kiwi_backlinks, kiwi_analytics, kiwi_memory_report, kiwi_context, kiwi_health_check, kiwi_suggestions, kiwi_embeddings, kiwi_graph_analytics, kiwi_velocity, kiwi_eval.
See MCP for full configuration details.
Access protocols
Every protocol flows through the same storage layer. Every write — regardless of how it enters — gets a git commit, a search index update, and an SSE broadcast.| Protocol | Use case | Example |
|---|---|---|
| REST API | Web frontend, scripts | curl localhost:3333/api/kiwi/file?path=index.md |
| MCP | AI agents (Claude, Cursor) | kiwifs mcp --root ~/knowledge |
| NFS | Docker, Kubernetes (native mount) | docker run --mount type=nfs,... |
| S3 | Backup, data pipelines | aws s3 sync s3://knowledge/ /backup/ |
| WebDAV | Windows mapped drives, legacy tools | Map Network Drive in Explorer |
| FUSE | Developer workstations | kiwifs mount --remote http://server:3333 ~/kiwi |
Provenance tracking
Know which agent run produced which knowledge:derived-from into the frontmatter automatically. Query later: “show me every page produced by run-249.”