I looked into how to store agentic state in a) a structured way that b) runs without any dedicated MCP memory/state servers and where I can get c) a clear diff-able audit trail of all state changes over time. Nothing that I could find fit the bill.

In https://github.com/commitspark/demo-agentic-mcp , I demo an implementation that fulfills these requirements by combining Claude agents with my previously published Commitspark library and its entirely Git-backed GraphQL API.

In the demo, two independent Claude agents are simulated that contribute to a task tracker. A third agent reviews any task changes and rolls back obviously bad ones. A full demo transcript is included in the README, including the agents' raw tool calls.

Task agent access to data happens via a small MCP server that exposes two Commitspark APIs (GraphQL API, schema API). These agents can then fetch the schema and author their own GraphQL calls, with GraphQL automatically enforcing written data is schema-conformant. The validator agent additionally has access to basic git functionality to view diffs and revert commits.

I'm looking for feedback specifically on: whether schema validation on shared agent state is a problem people actually have, or whether loosely-typed JSON + retries is good enough in practice.