MCP for Knowledge Islands knowledge bases on a local filesystem
Strong foundation with clear naming conventions (verb_noun pattern: kb_config, kb_read, kb_write, kb_delete, kb_list, kb_folder_create, kb_rename). All 7 tools have substantive descriptions (100-300+ chars, well above 20-char minimum). Input schemas present for all tools with proper JSON Schema structure including types, enums, and defaults. However, output schemas are not documented in the source code, descriptions mention what is returned but formal schema definitions are absent. Error handling guidance is minimal; descriptions lack recovery hints. Security model is well-designed (path confinement, allow-list enforcement, dry-run defaults on destructive ops) but not explicitly documented in tool descriptions.
Return the Knowledge Islands configuration for one declared knowledge base: resolved zone names, staging area names, the root-file read allow-list, and the raw .ki.toml content — plus the roster of every knowledge base this server may reach. Use this as an orientation step when working with an unfamiliar KB — it tells you which top-level folders correspond to each canonical zone (Calendar, Pillars, Resources, Streams, Admin) and which staging areas (+/ and -/) are configured. The zone map is derived from .ki.toml at server startup; if the file is absent, all zones use their canonical defaults. Returns a JSON object with: - kb (the alias whose detail follows) - zones: { Calendar, Pillars, Resources, Streams, Admin } - staging: { inbound, outbound } - rootFileAllowlist (exact paths available through kb_read) - kiConfigPresent (boolean) - kiConfigRaw (string — raw TOML or "(absent — all zones are defaults)") - knowledgeBases (every declared alias with its zone and staging names) Knowledge bases are addressed by alias throughout; filesystem paths are never returned.
Delete a file from a declared KB zone or staging root. dry_run defaults to true; root-file allow-list entries are never deletable.
Create a folder in a declared KB zone or staging root. Idempotent: succeeds when the folder already exists.
List files, folders, or Markdown notes under one declared zone or staging root. Returns a JSON object with entries and count. The KB root and configured root-file allow-list are never listable.
Output schemas not documented. Tool descriptions state what is returned (e.g., 'Returns a JSON object with entries and count') but formal output schema definitions are absent from source. LLMs cannot reliably parse responses or plan downstream tool chains without documented return types.
Error handling lacks recovery guidance. Descriptions do not explain what the LLM should do if a call fails (e.g., 'path not found, try kb_list() first to discover valid paths'). Errors are likely raw exceptions without actionable next steps.
Security model not exposed in tool descriptions. Path confinement, allow-list enforcement, and dry-run defaults are implementation details not mentioned in descriptions. LLMs cannot reason about safety guarantees or explain constraints to users.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | C | 65 | 2025-06-18+ | v2 |
Read one KB file and return its path, MIME type, encoding, size, and content. UTF-8 files return text; binary files return base64. For a Markdown file, part may select all content, YAML frontmatter, or body. Paths must be in a declared zone or staging root, except exact read-only entries in root_file_allowlist. The exception neither lists the root nor permits writes.
Rename or move a file within declared KB zones or staging roots. Refuses to overwrite an existing destination.
Create or overwrite a file in a declared KB zone or staging root. Use UTF-8 content for text and base64 for binary data. Writes are atomic; dry_run defaults to true. Root-file allow-list entries are never writable.
Parameter 'kind' in kb_list uses enum but lacks guidance on when to use each value. Description does not explain the difference between 'files', 'folders', and 'notes' or when an LLM should choose each.
No pagination or result limits documented. kb_list and kb_read could return large results; descriptions do not mention limits, pagination support, or guidance for recursive operations on deep directory trees.