hifriendbot/cogmemai-mcp

**It remembers what matters, stops any action that breaks the rules you set before it happens, and checks what your Ai did against what you asked. For assistants, agents, robots, vehicles and code.**
Every rogue-Ai story is the same story: an Ai acted, and nothing stood between the decision and the damage. CogmemAi is the part that stands there. It is a portable memory layer that gives any Ai system persistent recall across sessions, devices, users, and teams, captures knowledge autonomously even when your Ai forgets to save, enforces the rules you save before an action happens, and reviews finished work against your intent. **95.10% accuracy on LongMemEval, the top published score on the field's hardest long-term memory benchmark.** 91% on LoCoMo, above human performance (87.9%). Quantum-safe encryption. Works with Claude Code, Cursor, Windsurf, Cline, Continue, and any MCP-compatible tool. Switch editors, switch models, switch machines: your knowledge stays, and so do your rules. Not just one score on a test: the most complete, and the safest, Ai memory system available.
What's New in v3
The Safe Memory That Keeps Ai in Line (v3.32.3)
No code change. The package now says plainly what Guard and Review are for: the Ai you run should never be the one in the rogue-Ai headlines. Rules you save are enforced before an action happens, whether that action is a shell command, a message, a purchase or a change, and finished work is reviewed against what you asked. See Guard, Rule Packs and Intent.
A Character Budget for Recall (v3.32.0)
Long memories are worth keeping, and expensive to load ten at a time: every tool result stays in the conversation and is read again on each later turn. recall_memories now takes an optional max_chars. With a budget, the best-ranked memories come back complete and the rest come back as 400-character snippets that keep their id, type, subject and score, each marked truncated with its real length. Nothing is hidden: call recall_memories again with the same query and expand_ids: [..] to read any of them in full, or pass max_chars: 0 for everything. To make a budget the default for your own setup, set COGMEMAI_RECALL_MAX_CHARS (for example 8000) in the server's env; a max_chars on the call always wins. Replayed over a real working day of twelve searches, a budget of 8000 cut recall output by 42 percent. Without a budget, results are exactly what they were before. Save responses are lighter too: the related-memory pointer on save_memory is now a 300-character preview with its id, and the full text is still returned whenever the similarity is high enough to suggest a merge.
Sign In Instead of Pasting a Key, and Tool Annotations (v3.31.2)
The hosted endpoint https://hifriendbot.com/mcp/ now speaks OAuth 2.1: an MCP client that supports it (claude.ai, Claude Desktop, Cursor and others) discovers the authorization server from the endpoint's 401, registers itself, sends you to a CogmemAi consent page to sign in, and gets a token with PKCE; API keys keep working exactly as before. Every tool now carries MCP annotations (title, readOnlyHint, destructiveHint, idempotentHint), so clients can label tools and decide what to confirm.
Migrate: the Cloud Migration Playbook (v3.31.0)
npx cogmemai-mcp migrate assess --target aws (or azure, gcp) reads the repository and produces the migration in one run: an inventory (languages, frameworks, data stores, cloud SDKs, infrastructure as code, containers, CI, scheduled jobs, environment variable names, external hosts, secret-looking files; names and counts only, no file contents and never a secret value leave the machine), the migration scope document written as the project's intent (what moves, what stays, NEVER and MUST invariants, phases with a definition of done each, out of scope), and MIGRATION.md with the components table, phases, a ranked risk register, cost drivers and open questions. The plan and risks are stored as memories, and the migrate pack (16 process rules: inventory first, one workload at a time, lift then modernize, rehearsed rollback, data verified by counts and checksums, bulk syncs never delete without a dry run, secrets reissued and never exported, a single writer at cutover, source read-only thirty days before decommission) and the target cloud's pack are installed. Then, after each phase, cogmemai-mcp migrate gate " " reviews the work (commits, changed files, your notes, the planned steps) against the scope and passes at coverage 80 or more with no violations; every gate result is stored so the migration has a record. Three new cloud packs ship alongside: aws (20 rules), azure (18) and gcp (17), each in that cloud's own CLI shapes: no root or primitive roles, no long-lived keys, no admin ports or databases open to the internet, no public buckets, encryption and backups and deletion protection, detective controls and audit logs never disabled, org policies and SCPs as the floor, approved regions and data residency, budgets before the first workload, tags on everything. cogmemai-mcp migrate inventory prints the inventory alone, --dry-run shows what would be sent, --no-rules skips the packs, --force replaces an existing intent. The assessment runs through the MSGR gateway on your account's daily limit.