Enterprise DNAEnterprise DNA

MCP Servers

jaimenbell/vllm-ops-mcp

Read-only ops/health MCP server for a WSL2/systemd vLLM instance: liveness vs real-completion health tiers, GPU/VRAM, systemd state, live serve-flag introspection.

Visit site ↗

Our verdict

Not reviewed yet

We have not reviewed jaimenbell/vllm-ops-mcp yet

No one at Enterprise DNA has checked this listing against its sources. The description comes from public listings gathered automatically. Any fact below shows where it came from and when it was last checked.

How we review records

From the listing

About jaimenbell/vllm-ops-mcp

A read-only MCP server that exposes operational health data for a vLLM instance running under WSL2/systemd. It reports liveness versus real-completion health tiers, GPU/VRAM usage, systemd service state, and live serve-flag introspection.

Best for

Developers running vLLM on WSL2/systemd who need a lightweight, read-only health monitoring MCP server.

Use cases

  • Monitor vLLM instance health from an MCP-compatible client
  • Check GPU/VRAM utilization and systemd service status
  • Introspect live serve flags to verify runtime configuration

Notes

0 stars on GitHub. Last updated 2026-08-12. Licensed MIT.

Pros

  • Read-only design reduces risk of accidental state changes
  • Distinguishes liveness from actual completion readiness
  • Covers both system-level and model-serving health signals

Cons

  • Limited to WSL2/systemd environments
  • No write or control operations, only monitoring
  • Zero stars suggests minimal community validation

Key facts

What we have checked

Not checked yet. Dated facts such as prices, releases and repository activity appear here once we have confirmed them from a source.

How to use

How to set it up

As the listing publishes it. We have not run this install.

Tools exposed

  • list_models
  • get_gpu_status
  • get_service_status
  • get_serve_config
  • VLLM_OPS_MCP_BASE_URL
  • VLLM_OPS_MCP_MODEL
  • VLLM_OPS_MCP_WSL_DISTRO
  • VLLM_OPS_MCP_SERVICE_UNIT
  • VLLM_OPS_MCP_EXEC_SCRIPT_PATH
  • VLLM_OPS_MCP_SERVE_CONFIG_PATH
  • VLLM_OPS_MCP_NVIDIA_SMI_PATH
  • VLLM_OPS_MCP_RUNS_IN_WSL
  • VLLM_OPS_MCP_DEEP_RATE_LIMIT_PER_MIN
  • VLLM_OPS_MCP_LIVE

Clients the listing names (not checked here)

ChatGPT

Install

Add jaimenbell/vllm-ops-mcp to your client

Not verified yet

Our lab has not run this server yet. "Config checked" on a client means the recipe matches that client's documented config format; it does not mean we ran it.

Claude Code

Config checked

Run in your terminal (runs on your computer)

claude mcp add --transport stdio jaimenbell-vllm-ops-mcp -- uvx vllm-ops-mcp@0.1.0

Version 0.1.0 · From the Official MCP registry, read · Format checked against Claude Code's config docs

Claude Desktop

Config checked

Add to claude_desktop_config.json (runs on your computer)

{
  "mcpServers": {
    "jaimenbell-vllm-ops-mcp": {
      "command": "uvx",
      "args": [
        "vllm-ops-mcp@0.1.0"
      ]
    }
  }
}

Version 0.1.0 · From the Official MCP registry, read · Format checked against Claude Desktop's config docs

Cursor

Config checked

Add to .cursor/mcp.json (runs on your computer)

{
  "mcpServers": {
    "jaimenbell-vllm-ops-mcp": {
      "command": "uvx",
      "args": [
        "vllm-ops-mcp@0.1.0"
      ]
    }
  }
}

Version 0.1.0 · From the Official MCP registry, read · Format checked against Cursor's config docs

VS Code

Config checked

Add to .vscode/mcp.json (runs on your computer)

{
  "servers": {
    "jaimenbell-vllm-ops-mcp": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "vllm-ops-mcp@0.1.0"
      ]
    }
  }
}

Version 0.1.0 · From the Official MCP registry, read · Format checked against VS Code's config docs

Codex

Config checked

Add to ~/.codex/config.toml (runs on your computer)

[mcp_servers.jaimenbell-vllm-ops-mcp]
command = "uvx"
args = ["vllm-ops-mcp@0.1.0"]

Version 0.1.0 · From the Official MCP registry, read · Format checked against Codex's config docs

  • ChatGPT: ChatGPT connects only to remote servers that need no API key.

Recipes come from the server's entry in the official MCP registry. Check the package name before you run it, and keep keys out of shared files.

Works with

What jaimenbell/vllm-ops-mcp connects to

5 clients, each with how we know and when we checked.

Works withTypeHow we knowChecked
Claude CodeClientInstall recipe matches the client's documented formatRuns locally, version 0.1.0Config checkedClaude Code docs
Claude DesktopClientInstall recipe matches the client's documented formatRuns locally, version 0.1.0Config checkedClaude Desktop docs
CursorClientInstall recipe matches the client's documented formatRuns locally, version 0.1.0Config checkedCursor docs
VS CodeClientInstall recipe matches the client's documented formatRuns locally, version 0.1.0Config checkedVS Code docs
CodexClientInstall recipe matches the client's documented formatRuns locally, version 0.1.0Config checkedCodex docs

Sources

Where this comes from

No sources recorded yet. Each source we check is listed here with the date we checked it.

A source shows what was published when we checked it. It does not certify security, performance or a working installation. Read our method.

Changelog

What changed

No changes recorded yet. Releases, price changes and deprecations appear here, with their dates, once we track them for this record.

Free 27-page guide

Get the free Developer’s Field Guide

A 27-page field guide to the AI coding workflow with Claude. Claude Code, MCP servers, the prompt patterns that work, and what to delegate. Free.

Enter your work email. We send it straight over, plus a few short notes worth knowing. Unsubscribe any time.

No spam. Unsubscribe any time.

← Back to MCP ServersSubmit your own entry →