#1 AIUnknown
engram — alternative #1 to contextpulse
📇 🏠 🍎 🪟 🐧 - Local-first persistent memory for AI agents. SQLite + local embeddings (all-MiniLM-L6-v2), hybrid semantic + FTS5 recall, secret...
GitHub source
Recorded alternatives
Alternatives to contextpulse
Every candidate below sits in AI. What ends up on this page is decided entirely by a recorded score — not by bidding, not by editor taste. Review both records, check current vendor terms, then decide.
#2 AIUnknown
cogmemai-mcp — alternative #2 to contextpulse
📇 ☁️ 🍎 🪟 🐧 - Persistent cognitive memory for Claude Code. Cloud-first with semantic search, AI-powered extraction, and project scoping. Zero...
GitHub source
#3 AIUnknown
enquire-mcp — alternative #3 to contextpulse
📇 🏠 🍎 🪟 🐧 - Long-term memory for AI agents (Claude Code/Desktop, Cursor, ChatGPT, Codex, OpenClaw) backed by a local Obsidian markdown vault...
GitHub source
#4 AIUnknown
desktop-touch-mcp — alternative #4 to contextpulse
📇 🦀 🏠 🪟 - Windows desktop automation for LLM agents with entity-based actions instead of coordinate-only clicking. Uses UIA, CDP, screenshot...
GitHub source
#5 AIUnknown
mcp-server — alternative #5 to contextpulse
📇 🏠 🍎 🪟 🐧 - Project memory for AI coding sessions. Auto-captures checkpoints on git commits, branch switches, and inactivity, then provides...
GitHub source
#6 AIUnknown
memento-mcp — alternative #6 to contextpulse
📇 🏠 🍎 🪟 🐧 - Local-first persistent memory for AI coding agents. Captures facts, decisions, patterns, and architecture notes in SQLite (with...
GitHub source
#7 AIUnknown
rememb — alternative #7 to contextpulse
🐍 🏠 🍎 🪟 🐧 - Persistent memory for AI agents with sectioned entries (project/user/context/etc), semantic search, CLI, and per-project scope....
GitHub source
#8 AIUnknown
talkthrough-mcp — alternative #8 to contextpulse
🐍 🏠 🍎 🪟 🐧 - Turn narrated screen recordings (or any local video/audio) into agent-ready data: local Whisper transcript, scene keyframes, OCR...
GitHub source
Questions about this page
How were these alternatives selected?
Each candidate is a live catalogue record in the same primary category, picked by a deterministic score that Oryxen records in its catalogue: how many meaningful words the two listings share, whether their pricing classes oppose (a paid product against a free one), whether both are open source, and whether either record is featured. The same catalogue state always produces the same list — no randomness, no manual ranking.
Are these alternatives ranked by payment?
No. Rows are ordered only by the recorded score, highest first, with alphabetical ties — payment never influences the order, nothing here is paid placement, and Oryxen charges no listing or placement fee.
Always verify current terms with contextpulse directly — Oryxen records pricing classes, not live quotes.