Skip to main content
Glama
neuralnexustech

Cortex MCP

by neuralnexustech
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Cortex MCP

No user-submitted related servers found.

    Related Servers

    • Sugar

      Benjaminn581
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and write persistent, local-first memory across sessions and projects, with semantic search, global guidelines, and optional autonomous task execution.
      -

    • Sugar

      sibell349
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and write persistent, local-first memory so project decisions, preferences, and cross-project guidelines survive across sessions and can be retrieved by semantic search. Optionally also exposes a task queue for autonomous execution that draws on the same stored context.
      -

    • Sugar

      FrancescoBaran
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding agents to read and write persistent project and cross-project memory through semantic search, storing decisions, preferences, error patterns, and guidelines across sessions. Optionally exposes a task-queue server for autonomous task execution.
      -

    • engram

      coinstax
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides persistent project memory for AI coding agents, enabling context retention across sessions via event logging, briefing generation, and querying.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    B3.2/5.0

    Scored across 42 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: pipeline_* tools manage pipelines, role/agent tools manage permissions, add/update tools handle feature and test tracking. The main confusion is between cortex_health and cortex_auto_heal, which both check integrity and repair broken items, and cortex_check_reminders overlaps somewhat with both. The cortex_get_state vs cortex_get_detail distinction is clear.

    Naming Consistency4/5

    The set follows a consistent cortex_ prefix with verb_noun structure (add_feature, get_state, resolve_issue, pipeline_start). A few deviations exist: cortex_health is a bare noun instead of a verb_noun form, and cortex_tick_file uses the unusual 'tick' verb, but these are minor and decodable. Overall the pattern is predictable.

    Tool Count2/5

    42 tools is well beyond the 25+ threshold for 'too many' and requires a large surface area for an agent to internalize. The scope is broad (project state, features, tests, issues, knowledge base, skills, roles, pipelines, tokens, health), but much of it could be consolidated — e.g., pipeline alone takes 7 tools, and health/auto_heal/check_reminders could be unified. The count makes misselection more likely.

    Completeness3/5

    The core workflow is well covered: init → get_next_task → log_progress → tick_file → add/update tests → log/resolve issues, plus pipeline lifecycle has full start/pause/resume/cancel/plan/history coverage. However, there are notable gaps: no delete operations anywhere (no delete_feature, delete_test, delete_snippet, delete_issue), and no list/get_all tools — retrieval depends almost entirely on cortex_search or the compressed state. Read and removal paths are weak for a system that stores this much data.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources