1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
//! `mimir-mcp` — Mimir MCP (Model Context Protocol) server library.
//!
//! Exposes Mimir's current workspace-local canonical store to
//! **Claude** (Claude Desktop and Claude Code) via stdin/stdout
//! transport. Per Mimir's 2026-04-24 mandate, Claude and Codex are
//! the first target surfaces and future agents integrate through
//! draft/retrieval adapters. This crate remains the Claude MCP surface
//! until scope-aware adapters are specified; other MCP clients may
//! technically connect because the protocol is standard, but they are
//! out of scope for testing, support, and design tuning here.
//!
//! The library surface ([`MimirServer`]) is reusable in tests with the
//! in-memory `tokio::io::duplex` transport; the binary at `src/main.rs`
//! is a thin wrapper that wires `MimirServer` to stdio and a
//! tracing-to-stderr subscriber.
//!
//! ## Tools
//!
//! Phase 2.3 ships **nine** tools across three layers:
//!
//! Status:
//! 1. `mimir_status` — server health, store-open + lease-held flags.
//!
//! Read (workspace-required):
//! 2. `mimir_read` — Lisp `(query …)` execution; matched records
//! rendered as data-marked Lisp payloads.
//! 3. `mimir_verify` — read-only integrity check on a canonical log.
//! 4. `mimir_list_episodes` — paginated episode metadata.
//! 5. `mimir_render_memory` — single-record data-marked render.
//!
//! Write + lifecycle (lease-required):
//! 6. `mimir_open_workspace` — opens a `Store` and mints a write lease.
//! 7. `mimir_write` — commits a Lisp batch.
//! 8. `mimir_close_episode` — convenience wrapper for `(episode :close)`.
//! 9. `mimir_release_workspace` — drops the lease; reads continue to work.
//!
//! Read tools require an opened workspace store (set
//! `MIMIR_WORKSPACE_PATH` at startup, or call `mimir_open_workspace`).
//! Write tools additionally require a valid lease token returned by
//! `mimir_open_workspace`. See `crate::server` module docs for the
//! lease state machine.
//!
//! ## Stability
//!
//! The library API will move freely until `mimir-mcp` cuts a 1.0
//! release alongside the rest of the workspace. The on-wire MCP tool
//! surface (tool names, input schemas, output shapes) is what
//! agent-side prompts depend on; that surface gets a drift gate at
//! Phase 2.4 (`tool_catalog_drift`) and stricter `SemVer` commitments
//! once `v0.1.0-alpha.1` ships.
pub use ;