Request
Could you tag an MCP server release (and publish a zepai/knowledge-graph-mcp image) that includes add_memory's reference_time support?
Context
What we can offer
We run the MCP server in production against external Neo4j and needed reference_time for historical email/meeting ingestion, so we temporarily deployed a source build pinned to 993e081a6d7948a0d8851c12a5fbdbeb49fed862 (graphiti-core 0.29.3). Validated end-to-end and happy to share details:
- config schema: a 1.0.2-era
config.yaml (server/llm/embedder/database/graphiti sections, ${VAR} expansion) loads unchanged
- tool surface:
add_memory, get_episodes, delete_episode, search_memory_facts, get_status all present and compatible (note: get_episodes last_n → max_episodes rename since 1.0.2)
reference_time: ISO-8601 accepted, tz-naive→UTC, malformed rejected pre-queue; stored episode valid_at equals the supplied instant in Neo4j- boots clean on Python 3.11 with external Neo4j; episode-name identity and
delete_episode semantics unchanged from 1.0.2
We'd love to retire our source build for a published tag. Thanks for Graphiti!
Request
Could you tag an MCP server release (and publish a
zepai/knowledge-graph-mcpimage) that includesadd_memory'sreference_timesupport?Context
reference_timelanded onmainin feat(mcp): core-parity — bi-temporal, sagas, communities, filters, triplets, custom types #1553 (2026-06-08), with parse-before-queue validation — great design, callers get an immediate error instead of a silent background failure.1.0.2-standalone, pushed 2026-03-11) predates it, so image-based deployments silently stamp ingestion time on historical data.What we can offer
We run the MCP server in production against external Neo4j and needed
reference_timefor historical email/meeting ingestion, so we temporarily deployed a source build pinned to993e081a6d7948a0d8851c12a5fbdbeb49fed862(graphiti-core 0.29.3). Validated end-to-end and happy to share details:config.yaml(server/llm/embedder/database/graphiti sections,${VAR}expansion) loads unchangedadd_memory,get_episodes,delete_episode,search_memory_facts,get_statusall present and compatible (note:get_episodeslast_n→max_episodesrename since 1.0.2)reference_time: ISO-8601 accepted, tz-naive→UTC, malformed rejected pre-queue; stored episodevalid_atequals the supplied instant in Neo4jdelete_episodesemantics unchanged from 1.0.2We'd love to retire our source build for a published tag. Thanks for Graphiti!