Skip to main content
Glama
coder-ka

procm-mcp

by coder-ka
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to procm-mcp

No user-submitted related servers found.

    Related Servers

    • Shell-MCP

      kevinwatt
      A
      license
      B
      quality
      D
      maintenance
      A secure MCP server for executing whitelisted shell commands with resource and timeout controls, designed for integration with Claude and other MCP-compatible LLMs.
      20
      389 npm
      7
      MIT

    • MCP Shell Server

      mako10k
      A
      license
      B
      quality
      A
      maintenance
      A secure MCP server for shell operations, terminal management, and process control, enabling AI assistants to safely execute commands and manage interactive sessions.
      13
      161 npm
      6
      MIT

    • procm-mcp

      hunmer
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to securely create, manage, and monitor local processes such as dev servers, docker-compose, and test watchers, including restarting, checking status, and retrieving logs via MCP, HTTP, or WebSocket messaging.
      9 npm
      1
      MIT

    • mcp-sidecar

      lsequeiraa
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight, cross-platform MCP server for managing background processes. Enables AI coding agents to spawn, monitor, and interact with long-lived processes.
      MIT

    • interactive-process-mcp

      UserB1ank
      A
      license
      A
      quality
      C
      maintenance
      MCP server for managing interactive processes, enabling AI agents to start, interact with, and terminate long-running programs like SSH sessions, REPLs, and installers via read/write operations.
      8
      8
      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

    C2.8/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: starting, allowing, deleting, listing, retrieving info, stdout, stderr. No two tools have overlapping purposes; descriptions clearly differentiate them.

    Naming Consistency5/5

    All tool names follow a consistent verb-noun pattern in snake_case (e.g., start-process, get-process-info). Naming is predictable and uniform.

    Tool Count5/5

    With 11 tools, the server covers process lifecycle management comprehensively without redundancy. The count feels appropriate for the domain.

    Completeness4/5

    Core operations (start, list, info, restart, delete, output retrieval) are covered. Missing tools like graceful stop or sending input, but the set is sufficient for basic management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources