doobidoo/mcp-memory-service v10.56.0

v10.56.0 — Configurable Maintain Scan Limit + InsightGenerator Gap Filter

on GitHub

What's New in v10.56.0

Added

MCP_MAINTAIN_SCAN_LIMIT — configurable memory scan ceiling for the maintain cycle

The maintain consolidation cycle (Steps 5 and 6) previously scanned a hardcoded maximum of 500 memories for entity extraction and insight card generation. This was silently under-serving large deployments. v10.56.0 replaces this with a tunable env var:

# Default: scan up to 2000 memories per maintain cycle
MCP_MAINTAIN_SCAN_LIMIT=2000

# Remove the cap entirely (scan all memories)
MCP_MAINTAIN_SCAN_LIMIT=0

# Use a conservative limit for resource-constrained deployments
MCP_MAINTAIN_SCAN_LIMIT=500

Affects:

• Step 5 — entity extraction (EntityExtractor)
• Step 6 — insight card generation (InsightGenerator)

Fixed

InsightGenerator gap detector now skips metadata/status tags

The _detect_gaps method was treating operational system tags as knowledge domain gaps, generating spurious "Decision gap" insight cards for tags like __test__, automated, and conflict:unresolved. These tags are now in an EXCLUDED_GAP_TAGS frozenset and are silently skipped during gap analysis.

Tags excluded from gap detection:

• conflict:unresolved
• automated
• __test__
• temporary
• processed
• auto-generated
• insight-card

Files Changed

Upgrading

No breaking changes. Set MCP_MAINTAIN_SCAN_LIMIT in your environment if the default (2000) needs adjustment for your deployment. Deployments using Insight Cards (MCP_INSIGHT_CARDS_ENABLED=true) will immediately benefit from the gap filter fix — no configuration required.

Full CHANGELOG: https://github.com/doobidoo/mcp-memory-service/blob/main/CHANGELOG.md