cogmemai

Persistent cloud memory for Ai coding assistants.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Save Memory: Store a developer memory (fact, preference, decision, architecture detail). Memories persist across all Claude Code sessions and are available in future conversations.
  • 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 for absolute requirements li
  • List Rules: List all mandatory rules for the current project and/or globally. Rules are always-on memories that surface in every session.

What data it sees

Do you need an account

No: the server works without sign-in

Persistent cloud memory for Ai coding assistants. 33 MCP tools, 85% accuracy on LoCoMo benchmark. Semantic search, auto-skills, knowledge graph, quantum-safe encryption. Your Ai remembers everything across sessions, editors, and machines.

How to connect

How to connect cogmemai to Claude

The server address to paste into Claude settings:

https://cogmemai--hifriendbot.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect cogmemai to ChatGPT

The server address to paste into ChatGPT settings:

https://cogmemai--hifriendbot.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect cogmemai to Cursor

The server address to paste into Cursor settings:

https://cogmemai--hifriendbot.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (33)

Raw names from tools/list. Only developers need these.

save_memoryStore a developer memory (fact, preference, decision, architecture detail). Memories persist across all Claude Code sessions and are available in future conversations.
save_ruleSave 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 for absolute requirements like "NEVER do X" or "ALWAYS do Y".
list_rulesList all mandatory rules for the current project and/or globally. Rules are always-on memories that surface in every session.
delete_ruleDelete a mandatory rule by its memory ID. Use list_rules to find the ID first.
recall_memoriesSearch stored memories using semantic search. Returns memories ranked by relevance, importance, and recency. Use this to find relevant context from past sessions.
extract_memoriesExtract memories from a conversation exchange using AI. Send the developer message and assistant response, and the server identifies facts worth remembering (architecture decisions, preferences, bug fixes, etc.).
get_project_contextLoad 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 pass context to get memories most relevant to your current task.
list_memoriesList stored memories with optional filters by type, category, scope, or project.
delete_memoryDelete a specific memory by its ID. This is permanent.
update_memoryUpdate an existing memory's content, importance, or scope.
bulk_deleteDelete multiple memories at once by their IDs. Maximum 100 IDs per call. This is permanent.
bulk_updateUpdate multiple memories at once. Each item needs a memory_id and fields to update. Maximum 50 items per call.
get_usageGet current usage statistics — memory count, extractions this month, tier info, projects.
export_memoriesExport all memories as JSON. Use this to back up memories or transfer them to another project.
import_memoriesBulk import memories from a JSON array. Each memory needs at minimum a content field. Deduplication is applied automatically.
ingest_documentExtract 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 quickly build project context.
save_session_summarySave a summary of the current coding session. Captures what was accomplished, decisions made, and next steps. Stored as a session_summary memory for future reference.
list_tagsList all tags in use across your memories, with counts. Use this to see what threads/groups exist and find related memories by tag.
link_memoriesConnect 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 it, or connecting a preference to the pattern it led to.
get_memory_linksView all memories linked to a specific memory. Returns the relationship type and full memory details for each connection. Use this to explore the knowledge graph around a memory.
get_memory_versionsView 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 time.
get_analyticsGet a memory health dashboard with insights: most recalled memories, never-recalled memories, stale memories, growth trends, and breakdowns by type and category. Use this to identify cleanup opportunities and understand memory usage patterns.
promote_memoryPromote 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 — e.g., "user prefers tabs over spaces" or "always use Bun instead of npm".
consolidate_memoriesConsolidate related memories into fewer, richer memories. Finds clusters of memories sharing the same subject (3+ memories required), then uses AI to synthesize each cluster into 1-2 comprehensive facts. Originals are archived (not deleted) with full version history. Use dry_run=true to preview without making changes. Great for cleaning up memory clutter after many sessions.
save_taskCreate a task that persists across sessions. Tasks are tracked with status (pending, in_progress, done, blocked) and priority (high, medium, low). Use this to maintain continuity on multi-session work.
get_tasksGet 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 you left off.
update_taskUpdate a task's status, title, description, or priority. Use this to mark tasks as in_progress, done, or blocked as you work.
save_correctionSave a correction pattern — what went wrong and what the right approach is. These are surfaced automatically when similar situations arise in future sessions, helping avoid repeated mistakes.
set_reminderSet 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 after being shown.
get_stale_memoriesFind 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, or delete them.
get_file_changesShow 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 happened between sessions.
feedback_memorySignal whether a recalled memory was useful or irrelevant. Helps improve future recall quality over time. Use after recalling memories to indicate which were helpful vs noise.
generate_skillsManually trigger skill generation from your corrections, preferences, and patterns. Skills are behavioral directives that auto-improve how the AI works with you. CogmemAi also generates skills automatically when enough evidence accumulates — this tool lets you trigger it manually or preview candidates.