Skip to main content
Glama
Sign In
foxfirecodes

marker-watch-mcp

by foxfirecodes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to marker-watch-mcp

No user-submitted related servers found.

    Related Servers

    • codex-mcp-longrun

      woffko
      F
      license
      A
      quality
      B
      maintenance
      A local STDIO MCP server for running one bounded command and waiting for its final result, eliminating model-driven polling. Designed for builds, test suites, and other trusted foreground commands.
      3
      2
      -

    • bldr

      tek-cat
      A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight build daemon that exposes project build flows as MCP tools, enabling AI assistants to drive builds, check status, and react to results.
      MIT

    • bg-server-mcp-shell

      bgbruno
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for running long-running processes in PTY with real-time output streaming, enabling interactive dev servers, watch modes, and CLI tools.
      14 npm
      MIT

    • runkeep-mcp

      3xjn
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables management of long-running development processes (such as dev servers, compilers, and watchers) from MCP hosts. Provides tools to start, stop, restart, check status, view logs, and send input to managed processes.
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.3/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: status, specific version result, blocking wait, non-blocking wait state, and debug output. The only mild ambiguity is between get_build_status, get_build_wait, and await_build, which all involve build state/results and require reading descriptions carefully.

    Naming Consistency4/5

    The tool names consistently use snake_case and mostly follow a get_/await_/start_ verb pattern. The compound debug_get_live_output deviates slightly, and the repeated get_build_* prefix creates some similarity, but overall the naming is predictable and readable.

    Tool Count5/5

    Six tools is a well-scoped size for a build-monitoring server. Each tool covers a distinct aspect of querying or waiting for build results without redundancy or bloat.

    Completeness5/5

    The surface covers the key workflows: checking overall status, fetching a specific build result, waiting for the next completed build, starting a non-blocking wait, polling that wait, and debugging unresponsive builds. No critical missing operation is apparent for the stated purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources