Skip to main content
Glama
Wesley-Gomes93

engineering-mcp

by Wesley-Gomes93
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to engineering-mcp

No user-submitted related servers found.

    Related Servers

    • Daily Work MCP Server

      hsgui
      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.
      -

    • MCP Project Bridge

      Tenko-Star
      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

    • Devtrack MCP Server

      sraj0501
      F
      license
      A
      quality
      A
      maintenance
      DevTrack is a local developer-context MCP server that gives AI coding assistants access to your active ticket, commits, pending actions, writing voice profile, ticket history, and end-of-day summary. It exposes six read-only, non-destructive SQLite-backed tools over stdio. DevTrack runs locally and does not require the optional Python backend or a hosted MCP endpoint. https://devtrack.cloud.
      6
      2
      -

    • mcp-issue-tracker

      HamzaOuadid
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables interaction with a local SQLite-backed issue tracker, offering full CRUD operations (search, fetch, summarize, create, comment, close/reopen) with team-scoped visibility, authorization, rate limiting, and audit logging.
      MIT

    • Productivity Tracker MCP

      manasamadgul
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language task management including logging, updating, and summarizing productivity activities across multiple categories using a local SQLite database. It allows users to manage workflows and generate time-based summaries through standardized Model Context Protocol tools.
      1
      -
    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 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

    ActivityMaintained
    ResponsivenessNo issues

    Resources