kura

kura stores your Markdown and HTML documents in a single local SQLite file and makes them searchable by both humans and AI agents — with hybrid search tuned for Japanese text. No forced filing, no cloud, no account.

Quick Start (5 min)

Read the concept

Why kura

Notes pile up faster than any mandatory hierarchy can keep them tidy. kura never forces a filing decision: documents organize themselves through buckets, hierarchical tags (tech/db/sqlite), and wiki links ([[Title]]), with optional document paths (db/sqlite) when a folder-like name helps. Write a link before the target exists and it connects automatically the moment that page is created.

Retrieval is the hard part, and kura leans into it with a hybrid search pipeline built for Japanese: a morphological FTS index, semantic vector search over local embeddings, and local-LLM reranking — all inside one SQLite database.

Japanese-aware search

Keyword search (FTS5 + the sqlite-vaporetto morphological tokenizer), semantic search (sqlite-vec KNN over local embeddings), and hybrid search with local-LLM reranking.

Fully local

Your data lives in one SQLite file at ~/.kura/kura.db. Ollama and LM Studio are auto-detected; without them, keyword search still works.

Self-organizing

No forced filing. Buckets, hierarchical tags, and [[wiki links]] keep documents connected; document paths are optional, and the bucket root works as an inbox.

Built for AI agents

An MCP server (kura mcp) exposes search and CRUD as tools, and every read command speaks --json.

Graceful degradation

kura never hard-requires a model. With no LLM provider reachable, semantic search, reranking, clip formatting, tag suggestion, and query expansion each warn and fall back — while keyword search, document CRUD, links, and tags keep working. Run it on an airplane; you lose only the features that genuinely need a model.

Ready? Head to the Quick Start.