Engraphis 1.4: Smart MCP becomes the default

Engraphis 1.4 changed the default way agents talk to memory. Smart MCP became the zero-configuration gateway: compact, budget-aware, and designed around the actions an agent actually needs, while the complete Classic surface remained available for existing integrations.

What changed

• Smart MCP by default. engraphis-mcp now exposes nine compact tools for sessions, prompt-ready recall, durable memory, discovery, validated execution, and governed record changes.
• Classic compatibility. Integrations that depend on the former direct-tool surface can use engraphis-mcp-classic or the HTTP classic mode.
• Governed public writes. MCP, REST, import, sync, and extractor ingress enter an explicit review gate. Pending or quarantined records cannot influence prompt-visible recall or derived graph state.
• Planned recall. An optional deterministic planner adds bounded multi-query routing, priority-weighted fusion, post-rerank limits, stable context revisions, and diagnostics without changing the default single-query path.
• Broader agent support. The first-party Pi integration and the non-MCP adaptive-context endpoint extend the same service boundary to hosts that retain their own conversation history.

Upgrade notes

Existing v2 databases migrate automatically to schema 9 on first open. The NumPy-only core supports Python 3.9+; the dashboard, MCP, documents, Cloud Sync, and all extras require Python 3.10+.

Try the upgrade

Read the full changelog for the migration, authorization, and compatibility details. The Classic surface remains available when an existing client needs the former tool names.

Make the safe path the easy path.