A different approach from typical persistent-memory MCPs. Instead of a local
SQLite + embeddings store, the memory lives as plain files in a .ai-memory/
directory you commit to your repo (facts.jsonl, decisions/\*.md, gotchas.md).
Git is the sync layer — what one Claude/Cursor/Cline learns about a repo, the
next session (or a teammate's agent) picks up automatically.
5 MCP tools: get_rep
MCP server that exposes agent-memory-daemon to any MCP-compatible client — Kiro (CLI & IDE), Claude Desktop, Cursor, and others.
The daemon does the thinking (consolidation + extraction); this server is a thin filesystem bridge so agents can read, append, and search memory through the Model Context Protocol.
A local MCP server providing free network access capabilities including HTTP requests, web search, webpage content extraction, and optional screenshots, designed for integration with Claude Desktop or Claude Code.
A server that allows Claude to control audio playback on your computer, supporting MP3, WAV, and OGG files with features like play, list, and stop commands.
MCP server for HamQTH.com — callsign lookup, DX cluster spots, Reverse Beacon Network, DXCC resolution, and more through any MCP-compatible AI assistant.
