semantic-memory-mcp

Search, recall, and store vectorized memories with file-based fallback.

15|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/komluk/scaffolding --skill semantic-memory-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: semantic-memory-mcp
Source: https://github.com/komluk/scaffolding/tree/main/skills/semantic-memory-mcp
Command: npx skills add https://github.com/komluk/scaffolding --skill semantic-memory-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Agents often miss relevant past findings, decisions, and bug root-causes because semantic memory is unused or underutilized; this Skill ensures agents proactively search, recall, and store concise vectorized memories so future investigations and decisions are faster and more accurate.

Core Features & Use Cases

  • Proactive Memory Use: Rules for when to run semantic_search and semantic_recall at task start and during unexpected errors to surface relevant context.
  • Structured Memory Writing: Guidance for write-capable agents to store reusable insights with content_type, tags, and brief rationale so others can act on them.
  • Fallback and Safety: File-based fallback when MCP services are unavailable and quality gates to avoid storing speculative or task-specific noise.
  • Use Case: A debugger encountering an intermittent "attached to a different loop" error runs semantic_search to find prior fixes, retrieves a formatted memory via semantic_recall, and semantic_store saves the verified root cause for future agents.

Quick Start

Ask the agent to proactively search and recall related memories for your task and, if it discovers a verified reusable insight, store it with tags and a brief rationale.

Frequently Asked Questions about semantic-memory-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enable agents to use semantic memory for recalling past debugging decisions?

Enable agents to proactively run semantic_search and semantic_recall operations at task start or during unexpected errors to retrieve past debugging decisions and relevant context from the semantic vector memory.

What is the best way to store reusable agent insights in a semantic vector memory?

Use semantic_store write operations to save verified insights by attaching content_type, tags, agent_name attribution, and a brief rationale, ensuring future agents can effectively query and reuse the stored context.

How do multi-agent workflows handle semantic memory search and recall for architecture decisions?

Multi-agent workflows handle architecture decisions by applying semantic memory policies across agents, triggering semantic_search and semantic_recall to surface relevant historical context and recurring patterns before finalizing design choices.

Does semantic memory management work when MCP services are unavailable?

Yes, semantic memory management supports file-based fallback when MCP services are unavailable, allowing agents to maintain read and write operations for context storage without service interruption.

How can I prevent agents from storing speculative noise in a semantic store?

You can prevent speculative noise by applying quality gates that block semantic_store operations for unverified data, ensuring only confirmed, reusable insights with clear rationale are committed to the semantic store.

When should agents use semantic_recall instead of semantic_search during recurring pattern discovery?

Agents should use semantic_recall to retrieve formatted memory entries after semantic_search identifies potential matches, optimizing recurring pattern discovery by extracting precise context rather than broad vector matches.