Skip to main content
Glama
Sign In
cogmemai-mcp

cogmemai-mcp

by hifriendbot
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to cogmemai-mcp

No user-submitted related servers found.

    Related Servers

    • Ramorie

      kutbudev
      A
      license
      Not graded
      quality
      B
      maintenance
      Persistent project memory and task management for AI coding agents through MCP. Lets Claude Code, Cursor, Codex and other MCP clients save decisions and bug fixes, search relevant context, and reuse it across sessions.
      1
      MIT

    • memex

      jurgentaylor0309
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI coding agents persistent, cross-session memory by storing task insights as interlinked markdown knowledge cards and recalling relevant ones before new work begins. Uses plain files and git sync instead of a vector database or embeddings, and exposes this through MCP tools for Claude Code, Cursor, VS Code Copilot, Codex, Windsurf, and other clients.
      13 npm
      ISC
    • forgein

      forgeinofficial

      forgeinai
      F
      license
      Not graded
      quality
      D
      maintenance
      Persistent context layer for AI coding assistants. Sync memory files from Claude Code to ChatGPT, Gemini, Cursor, Windsurf, and Copilot via a native MCP endpoint. Bearer token auth, JSON-RPC 2.0 over stateless HTTP. Free tier available.
      -
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    A3.8/5.0

    Scored across 35 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose, with descriptions that precisely define scope (e.g., bulk_delete vs delete_memory, extract_memories vs extract_principles). No overlapping or ambiguous tools exist.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern using snake_case (e.g., save_memory, get_analytics, list_rules). No mixing of conventions or irregular naming.

    Tool Count5/5

    35 tools is appropriate for a comprehensive memory management system covering memories, rules, skills, tasks, reminders, analytics, and import/export. Each tool addresses a specific operation without redundancy.

    Completeness3/5

    Core CRUD for memories is complete, but several operations are missing: no delete_task, no update_rule or delete_rule, no unlink_memories, no list/delete for reminders or skills. These gaps could cause agent failures in managing the full lifecycle.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources