Skip to main content
Glama
ellmos-ai

ellmos-servercommander-mcp

Official
by ellmos-ai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ellmos-servercommander-mcp

No user-submitted related servers found.

    Related Servers

    • tibet-pol-mcp

      Humotica
      A
      license
      A
      quality
      D
      maintenance
      MCP server for running infrastructure health checks with TIBET provenance. It enables users to define, execute, and audit process health checks with dependency chaining and drift tracking.
      6
      MIT

    • health-monitor-mcp

      oaslananka
      A
      license
      A
      quality
      B
      maintenance
      MCP server for monitoring health of MCP servers, GitHub Actions, GitLab pipelines, and HTTP endpoints with health history, TLS expiry, assertions, diagnostics, and alerts.
      22
      334 npm
      2
      MIT

    • ops-agent-toolkit-mcp

      Jeromefromcn
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing read-only operational tools (logs, metrics, traces, service health, config) for troubleshooting an environment, with one exception for toggling chaos scenarios.
      MIT

    • automation-health-mcp

      chainwright
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for auditing automation health, finding failures, stale logs, and non-functional endpoints that report success while quietly failing.
      7
      MIT

    • mcp-incident-copilot

      ShreyAC962
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that provides guarded, audited, read-only access to ops tooling (alerts, metrics, logs, deploys, runbooks) and a triage agent that diagnoses incidents end-to-end with CI-verified root cause analysis.
      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

    B3/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a fairly distinct area: deploy vs deploy_status differ by planning versus status inspection, and the four mail tools split cleanly along list/read/send/search. The main risk is sc_deploy vs sc_deploy_status, which could be confused at a glance, but descriptions clarify the boundary.

    Naming Consistency4/5

    All tools share an sc_ prefix and snake_case, with mostly predictable noun_verb ordering (sc_mail_list, sc_health_check, sc_logs_analyze). sc_deploy is a bare verb outlier and the mail_* group reads as noun_action rather than verb_noun, but the scheme is readable and consistent overall.

    Tool Count4/5

    Eight tools is well within a sensible range for a server-commander surface spanning deploy, mail, logs, and health. No obvious redundancy or padding, though half the set is devoted to mail operations that are still alpha stubs.

    Completeness3/5

    Mail coverage (list/read/send/search) and deploy (plan + status) are reasonably complete, but several operations are explicitly non-functional alpha status endpoints (send 'does not send yet') and there is no log tailing/filtering beyond one-shot analysis. The server-commander domain lacks service restart, config, or process-management operations, leaving notable gaps.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources