Skip to main content
Glama

Related Servers

Alternatives to engineering-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables recording, querying, and summarizing daily work entries with tags using a local SQLite database. Supports work logging, search, timeline queries, tag management, and automated reminders for tracking daily tasks.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables multi-project workspaces to share structured notes, API contracts, and handoff messages via a local SQLite database, with versioning and read tracking.
      GPL 3.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables an engineering assistant to persist and query local CAD review context—named features, notes, tags, and revision-bound decisions with their requirements and evidence—in SQLite by artifact, entity, text, or tag, marking records stale against a caller-supplied revision. It never opens the CAD file, so it works on a laptop with no CAD software or other server running.
      5
      137 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables parallel coding agents to coordinate through a fenced ticket queue with atomic claim-and-dispatch, lease-based locks, dependency-aware scheduling, typed links, batch ticket creation, and hash-chained history over a shared SQLite file.
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables developers to maintain a local engineering journal, log work manually or from git history, and let AI assistants query, summarize, and draft standup updates, changelogs, and retro notes.
      MIT

    TDQS

    B3.2/5.0

    Scored across 23 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action (e.g., work_upsert_project vs work_upsert_ticket vs work_upsert_task). Lifecycle tools like investigate_open/add_finding/conclude and qa_record_run/record_bug are clearly separate, and the reporting and knowledge tools have unique roles. No two tools appear to do the same thing.

    Naming Consistency4/5

    The naming pattern is generally domain_prefix + verb_noun (e.g., work_upsert_ticket, qa_record_run). Minor deviations include 'work_list' lacking an explicit object, 'work_board' and 'time_metrics' using nouns as commands, and 'eng_route' not following the domain-prefix structure. Overall, it's predictable and readable.

    Tool Count4/5

    With 23 tools, the server is on the heavier side, but the count is justified by the breadth of domains covered (work, time, investigation, knowledge, QA, reporting, routing). Each tool serves a specific purpose, and the volume aligns with the comprehensive engineering management scope.

    Completeness4/5

    The tool surface covers the full lifecycle for tickets, tasks, projects, investigations, time tracking, and QA evidence, including reporting and knowledge handoff. Minor gaps include the absence of explicit delete or archive operations on tickets/projects, and no bulk actions, but these are not critical for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues