Skip to main content
Glama
flores-ac

cursor-cortex

by flores-ac
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to cursor-cortex

No user-submitted related servers found.

    Related Servers

    • engrams

      stevebrownlee
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI assistants persistent, queryable project memory for decisions, patterns, and rules, reducing the need to re-explain context in every prompt.
      11
      Apache 2.0

    • open-zk-kb

      mrosnerr
      A
      license
      Not graded
      quality
      A
      maintenance
      Gives AI assistants persistent, shared memory using the Zettelkasten method, so they retain corrections, preferences, and decisions across sessions and across tools via local, hybrid search.
      723 npm
      7
      MIT

    • recall

      andrewhomeyer
      A
      license
      A
      quality
      D
      maintenance
      Gives AI assistants a persistent memory across conversations, allowing them to remember user preferences, notes, and facts between chats.
      6
      54 npm
      MIT

    • BuildAutomata Memory MCP

      brucepro
      F
      license
      Not graded
      quality
      D
      maintenance
      Provides AI agents with persistent, searchable memory that survives across conversations using semantic search, temporal versioning, and smart organization. Enables long-term context retention and cross-session continuity for AI assistants.
      14
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 38 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but a few like search_branch_notes and comprehensive_knowledge_search overlap in search functionality, and archive_branch_note/clear_branch_note both handle archiving. However, descriptions clarify boundaries well enough to avoid serious misselection.

    Naming Consistency3/5

    The server consistently uses snake_case, but conventions vary: many tools follow verb_noun (read_branch_notes, generate_commit_message) while others are noun phrases (enhanced_branch_survey, timeline_reconstruction, graphql_knowledge_query). This mixed pattern makes tool names slightly less predictable.

    Tool Count2/5

    With 38 tools, this server is over-scoped. Many tools are process sub-steps (e.g., request_thinking_guidance, add_perspective, complete_synthesis_step) that could be consolidated or parameterized. The high count increases cognitive load and feels excessive for a single MCP server.

    Completeness4/5

    The tool set covers the full knowledge lifecycle: creating, reading, updating, searching, archiving, and sharing knowledge, plus specialized analysis and decision workflows. Minor gaps exist (e.g., no delete for tacit knowledge, no update for context files after creation), but core workflows have no dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources