Skip to content

Release v1.3.2

Latest

Choose a tag to compare

@github-actions github-actions released this 30 Jul 15:29
7223779

Summary

The MCP server grows from static data checks into system understanding: it can now deduce what the system in an event store is and is for from the registered event types, suggest how the event model should evolve, and answer natural-language questions like "show all employees with all details" by projecting events on demand — nothing registered, nothing written.

Added

  • describe_system tool that deduces the system in an event store — clustering event types into entities, placing every event in its entity's lifecycle, and mapping read surfaces and automations — with narrative guidance for describing the system and telling its story
  • suggest_next_event_types tool that finds lifecycle gaps (no explicit creation, a life without an end, facts frozen at creation) and suggests grounded event types to introduce next
  • run_ad_hoc_projection tool that folds events into per-event-source instances on demand with AutoMap semantics, answering ad-hoc queries without registering a projection
  • MCP prompts describe_system, suggest_next_event_types, and query_system packaging the workflows for clients that surface prompts
  • Documentation for the new capabilities in the design-time docs, README, and getting started

Changed

  • Updated all dependencies to their latest versions, including Chronicle 16.11.1 and the MCP SDK 2.0.0
  • The default connection string is now chronicle://localhost:35000 — Chronicle 16.11 removed the disableTls flag; the client always uses TLS, with skipTlsValidation controlling certificate validation