# cogmemai-mcp The smart memory layer for everything Ai. 95.10% LongMemEval (highest published). - **Type:** MCP server - **Trust:** 60/100 (B), scored on the package rubric - **Verification:** community-indexed — nobody has claimed this listing - **Version:** 3.23.0 - **Author:** io.github.hifriendbot - **License:** MIT - **npm:** cogmemai-mcp - **Source:** https://github.com/hifriendbot/cogmemai-mcp - **Compatible clients:** claude-code, cursor, copilot, gemini (basis: transport) ## Trust 60/100 (B), scored on the package rubric - Publisher verified: no - Install scripts: nothing suspicious found - Prompt-injection scan: not run - Obfuscation scan: not run - Evidence age: 1 day ## Security scan - **Status:** clean - **Scanned:** 2026-09-01T05:02:14.340Z - **Version scanned:** 3.23.0 - **CVEs:** none found by OSV at scan time ## Tools 37 declared. Statically extracted from the shipped source — a floor on the surface, not a census. - `save_memory` — Store a developer memory (fact, preference, decision, architecture detail). Memories persist across all Claude Code sessions and are available in future convers - `save_rule` — Save a mandatory rule that will ALWAYS be followed in every session. Rules bypass scoring and decay — they are injected into every conversation, every time. Use - `list_rules` — List all mandatory rules for the current project and/or globally. Rules are always-on memories that surface in every session. - `delete_rule` — Delete a mandatory rule by its memory ID. Use list_rules to find the ID first. - `preflight` — Proactive recall. Call this BEFORE making any suggestion, recommendation, or action plan. Sends the topic to a fast keyword search and returns any relevant prio - `recall_memories` — Search stored memories using semantic search. Returns memories ranked by relevance, importance, and recency. Use this to find relevant context from past session - `extract_memories` — Extract memories from a conversation exchange using AI. Send the developer message and assistant response, and the server identifies facts worth remembering (ar - `get_project_context` — Load top memories for the current project plus relevant global memories. Use at the start of a session to get full context from previous sessions. Optionally pa - `list_memories` — List stored memories with optional filters by type, category, scope, or project. - `delete_memory` — Move a memory to the trash by its ID. Trashed memories are hidden from recall and restorable with restore_memory for 30 days, then purged permanently. - `restore_memory` — Restore a trashed (deleted) memory by its ID. Works within 30 days of deletion, before the trash is purged. Use list_trash to find restorable memories. - `list_trash` — List trashed (deleted) memories, newest first, with days remaining before each is purged permanently. Restore any of them with restore_memory. - `update_memory` — Update an existing memory's content, importance, or scope. - `bulk_delete` — Delete multiple memories at once by their IDs. Maximum 100 IDs per call. This is permanent. - `bulk_update` — Update multiple memories at once. Each item needs a memory_id and fields to update. Maximum 50 items per call. - `get_usage` — Get current usage statistics — memory count, extractions this month, tier info, projects. - `export_memories` — Export all memories as JSON. Use this to back up memories or transfer them to another project. - `import_memories` — Bulk import memories from a JSON array. Each memory needs at minimum a content field. Deduplication is applied automatically. - `ingest_document` — Extract memories from a document by splitting it into chunks and processing each one. Great for onboarding — feed in READMEs, architecture docs, or API specs to - `save_session_summary` — Save a summary of the current coding session. Captures what was accomplished, decisions made, and next steps. Stored as a session_summary memory for future refe - `list_tags` — List all tags in use across your memories, with counts. Use this to see what threads/groups exist and find related memories by tag. - `link_memories` — Connect two related memories with a named relationship. Use this to build a knowledge graph — e.g., linking a bug fix to the architecture decision that caused i - `get_memory_links` — View all memories linked to a specific memory. Returns the relationship type and full memory details for each connection. Use this to explore the knowledge grap - `get_memory_versions` — View the edit history of a memory. Shows all previous versions with timestamps and what changed. Useful for understanding how a decision or fact evolved over ti - `get_analytics` — Get a memory health dashboard with insights: most recalled memories, never-recalled memories, stale memories, growth trends, and breakdowns by type and category - `promote_memory` — Promote a project-scoped memory to global scope so it applies across all projects. Use this when you discover a preference or pattern that should be universal — - `consolidate_memories` — Consolidate related memories into fewer, richer memories. Finds clusters of memories sharing the same subject (3+ memories required), then uses AI to synthesize - `save_task` — Create a task that persists across sessions. Tasks are tracked with status (pending, in_progress, done, blocked) and priority (high, medium, low). Use this to m - `get_tasks` — Get tasks for the current project. Returns tasks filtered by status — defaults to showing pending and in_progress tasks. Use at session start to pick up where y - `update_task` — Update a task's status, title, description, or priority. Use this to mark tasks as in_progress, done, or blocked as you work. - `save_correction` — Save a correction pattern — what went wrong and what the right approach is. These are surfaced automatically when similar situations arise in future sessions, h - `set_reminder` — Set a reminder that surfaces automatically at the start of your next session. Use for follow-ups, things to check, or deferred work. Reminders auto-archive afte - `get_stale_memories` — Find memories that may be outdated based on age and access patterns. Returns memories that haven't been recalled or updated recently, so you can review, update, - `get_file_changes` — Show what files changed since your last session. Compares the current git state to a snapshot saved when your previous session ended. Helps you understand what - `feedback_memory` — Signal whether a recalled memory was useful or irrelevant. Helps improve future recall quality over time. Use after recalling memories to indicate which were he - `generate_skills` - `extract_principles` ## Install **Verdict: review** — Installable, but 1 thing to check first: No publisher has proved control of this listing; it is indexed, not vouched for. **Cautions** (coverage gaps and advisories — never blocking) - No publisher has proved control of this listing; it is indexed, not vouched for. **Config** (claude-code): ```json "{\n \"mcpServers\": {\n \"cogmemai\": {\n \"command\": \"npx\",\n \"args\": [\n \"-y\",\n \"cogmemai-mcp\"\n ],\n \"env\": {\n \"COGMEMAI_API_KEY\": \"\"\n }\n }\n }\n}" ``` **Credentials it will ask for** (names only — Forge never holds a value): - `COGMEMAI_API_KEY` — Cogmemai API Key (required) Placeholders only. Forge never holds, brokers, or transmits a credential value — replace each in your own config file. Do not send a value back to Forge; no Forge endpoint accepts one. - This entry needs 1 credential (1 required). The generated config carries placeholders, so it will fail in the editor rather than at runtime if they are left unset. ## Blast radius Extensive blast radius — deletes data; holds an api key. - Floor 54, ceiling 54 (tier: extensive) - This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score. ## Machine-readable views of this entry - Signed JSON: https://forgeregistry.com/api/v1/packages/cogmemai-mcp - Install plan: https://forgeregistry.com/api/v1/packages/cogmemai-mcp/install-plan - Alternatives: https://forgeregistry.com/api/v1/alternatives/cogmemai-mcp - HTML page: https://forgeregistry.com/registry/cogmemai-mcp - MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan` ## About this document Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.