Skip to main content
Glama
BezaCore-Labs

never4ga-mcp

Official
by BezaCore-Labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to never4ga-mcp

No user-submitted related servers found.

    Related Servers

    • RepoRecall

      esannkv
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides persistent, local-first memory for coding agents with Markdown as the source of truth, exposed via CLI, loopback API, MCP, and Codex hooks for context retrieval and durable writes.
      MIT

    • goldfish

      Vibes-lj
      A
      license
      A
      quality
      B
      maintenance
      Unifies cited transcript search, auto-compressed session context, and hand-curated notes behind a single MCP server, letting AI coding agents look up past discussions, check what was just happening, and store or recall durable facts across projects.
      7
      MIT

    • promem-mcp

      DIP-RO
      A
      license
      B
      quality
      A
      maintenance
      Enables AI coding agents to maintain persistent project context, including rules, decisions, environment intelligence, and Git history, using a local-first MCP server with automatic project detection and token-efficient retrieval.
      13
      MIT
    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

    A3.6/5.0

    Scored across 15 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: session lifecycle (startup, checkpoint, wrap), vault retrieval (search, get_concept, context_focus), and work tracker operations (search, get, create, update, comment) are separated by domain prefixes and descriptions. Overlap is minimal, and the descriptions clarify boundaries.

    Naming Consistency4/5

    All tools share the never4ga_ prefix and snake_case, which makes them groupable, but the action ordering varies: some use noun_verb (work_get, workspace_resolve), others verb_noun (get_concept), and several are bare verbs/nouns (wrap, decide, search). This is mostly consistent with minor deviations.

    Tool Count5/5

    15 tools is at the upper end of the ideal range, but each tool maps to a distinct operation in session management, vault access, and work tracking. The set is well-scoped with no obvious redundancy.

    Completeness4/5

    Core lifecycle and retrieval workflows are covered, including session start/checkpoint/wrap, vault search and concept retrieval, and work item create/read/update/comment. Minor gaps exist (e.g., no work item delete or direct concept update/delete), but these may be intentional or manageable via other tools.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources