Skip to main content
Glama
FilippoPilo

cortex-connector

Related Servers

Alternatives to cortex-connector

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      This MCP server exposes Sekha memory tools (store, search, update, etc.) to any MCP-compatible client, enabling persistent conversation memory across Claude Desktop, Claude Code, and other applications.
      2
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      @memofs/mcp-server lets AI coding agents (Claude Code, Claude Desktop, Codex, Cursor, opencode, Gemini CLI, GitHub Copilot, Zed, and any other MCP client) securely read and write MemoFS memory through standard Model Context Protocol tools.
      6
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Official Model Context Protocol (MCP) server for Cogniz Memory Platform. Enables AI assistants like Claude to store and retrieve memories across conversations.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A stdio MCP server providing everyday tools and Markdown skills for the Sesha agent, enabling notes, web research, coding, docs, scheduling, and safety/governance.
      GPL 3.0
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides a hosted remote MCP server that lets compatible AI clients retrieve and save durable context, checkpoints, operating rules, project notes, and permission-controlled templates for continuity across ChatGPT, Claude, IDEs, coding agents, and other AI tools. It enables token-efficient startup and resume handoffs so users can move projects between tools without rebuilding detailed prompts each session.
      1
      -
    • F
      license
      Not graded
      quality
      B
      maintenance
      Provides a self-hosted shared memory service that lets AI agents capture and recall durable facts, decisions, and context across multiple tools and MCP-capable clients.
      3
      -

    TDQS

    A3.9/5.0

    Scored across 7 tools

    Disambiguation4/5

    Most tools have distinct purposes: conflicts, forget, write, status, and fetch are clear. However, search, fetch, and recall all involve retrieving memory content and could overlap in practice, requiring careful description reading to pick the right one.

    Naming Consistency2/5

    Naming is inconsistent: some tools use the cortex_ prefix (cortex_conflicts, cortex_forget, cortex_recall, cortex_write, cortex_write_status) while others do not (search, fetch). The pattern is not uniform, and cortex_write_status breaks the simple verb_noun structure.

    Tool Count5/5

    Seven tools is a reasonable, focused set for a persistent memory server. Each tool covers a needed operation without feeling bloated or sparse.

    Completeness4/5

    The toolset covers the core memory lifecycle: write, read via search/fetch/recall, delete via forget, plus conflict and status handling. An explicit update or list-all operation is missing, but write can likely serve as upsert and search covers listing, so the surface is largely complete.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues