Skip to main content
Glama
jaimenbell

vllm-ops-mcp

by jaimenbell
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to vllm-ops-mcp

No user-submitted related servers found.

    Related Servers

    • runtime-inspector-mcp

      ludi-uni
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only MCP server to inspect allowlisted Docker containers, systemd services, JSONL logs, and HTTP health endpoints without arbitrary shell access.
      MIT

    • mcp-diag

      Leonelito08
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only diagnostic MCP server that exposes system stats, Docker status, OOM events, container logs, Sidekiq queues, and local Chatwoot health checks for Claude to review a Hetzner server.
      -
    • Local AI MCP by TMHSDigital

      Local AI MCPofficial

      TMHSDigital
      A
      license
      A
      quality
      A
      maintenance
      Unified MCP server for managing local model runtimes (Ollama, LM Studio, etc.), enabling provider-agnostic discovery, lifecycle management, hardware-fit checks, and delegated inference.
      16
      18 npm
      Creative Commons Attribution Non Commercial No Derivatives 4.0 International

    • platform-mcp-server

      kamroy
      F
      license
      A
      quality
      C
      maintenance
      Read-only MCP server that exposes Kubernetes platform state (tenants, pods, SLOs, ArgoCD applications, chaos schedules, and catalog services) to AI agents, enabling natural language queries about cluster health and configuration.
      6
      -

    • hpc-support-mcp

      PetitSphincter
      A
      license
      Not graded
      quality
      C
      maintenance
      A read-only MCP server exposing SLURM, GPFS, Prometheus (node exporter + DCGM GPU metrics) and generic Elasticsearch exploration as diagnostic tools for LLM-based HPC support assistants.
      Apache 2.0
    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

    A4.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    Tools target distinct resources (health, models, GPU, service, config) and actions. The only potential overlap is between check_health(deep=true) and test_completion, but their purposes are clearly differentiated as health probe vs. user-driven test.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: check_health, list_models, test_completion, get_gpu_status, get_service_status, get_serve_config. No mixed conventions or vague verbs.

    Tool Count5/5

    Six tools is well-scoped for a vLLM operations server. Each tool covers a distinct operational need without redundancy or bloat, fitting comfortably in the ideal 3-15 range.

    Completeness4/5

    The tool set covers core read-only monitoring (health, models, GPU, service, config) and testing. Minor gaps include lack of service control (start/stop/restart) and log retrieval, but these are likely intentional given the read-only nature of the service status tool.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources