memstead-mcp 0.11.0

MCP server for Memstead — exposes the typed entity-graph engine over JSON-RPC stdio. Default build produces the full `memstead-mcp` binary (multi-mem, git-backed); `--no-default-features` builds the lean folder + archive surface.
Documentation 
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

//! Tool parameter structs for the agent-facing MCP tools.
//!
//! Parameter structs derive `Deserialize` + `JsonSchema` for rmcp tool routing.
//! These structs are shared between the lean `FilesystemMcpServer`
//! (here in `memstead-mcp`) and the full `McpServer`
//! ([`crate::server::McpServer`]). Full-only tool parameters
//! (mem-lifecycle family) live in [`crate::lifecycle`].
//!
//! Workspace-policy mutation is **not** an MCP surface. Which mems may
//! be created or deleted, and which cross-mem links are granted, is the
//! operator deciding what an agent is allowed to do — putting those
//! switches on the agent's own tool surface would hand the constrained
//! party the keys to its constraints. Policy is edited on operator
//! surfaces — `memstead workspace <action>` and the
//! operator-authenticated web API — and a policy-gated mutation refuses
//! with the exact command to report. External agents that need to
//! discover mems read `memstead_health.writable_mems` and
//! `memstead_health.read_mems`.
//! **Mem lifecycle** (create/delete a whole mem) is a distinct
//! concept and also lives on the MCP surface as `memstead_mem_create`
//! / `memstead_mem_delete` — gated by workspace-level
//! `[mem_management]` allowlists.

pub mod admin;
pub mod graph;
pub mod mutation;