mnvitop-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_hostsA | List the configured GPU hosts: display name and ssh target. No remote calls; use it to learn the names the other tools accept. |
| fleet_statusA | Live GPU status of every configured host (or just the named ones), probed now over ssh; takes 1-5 s. Returns a fleet summary line, then per host: free and busy GPU counts, free VRAM, load, and per GPU the utilisation, VRAM used and free, temperature and (with processes=true) the largest processes with user, pid, VRAM, age and command. A GPU is busy when a process holds it or it has more than five percent of its memory taken. Hosts that do not answer come back with ok=false and an error instead of raising. |
| find_gpusA | Find where a job that needs Call this first for any placement question. Returns found, a summary line, placements best first (the least loaded host that has enough idle GPUs, with the GPU indices to use), and when nothing fits, alternatives: hosts with fewer idle GPUs and busy GPUs that still have the VRAM (shared with someone else's job, so only for small experiments). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: listing configured hosts, querying live status, and finding placement for GPU jobs. No overlap or ambiguity between them.
Two tools use verb_noun pattern (list_hosts, find_gpus) while fleet_status is a noun phrase, creating a minor inconsistency. However, the names are short, clear, and follow a predictable theme of fleet management.
Three tools are ideal for a focused GPU fleet monitoring and placement server. Each tool serves a necessary and non-redundant function, and the count is well within the recommended range.
The server covers listing, status probing, and placement suggestion, which are core to its stated purpose. Minor gaps exist (e.g., no tool to modify host configuration or trigger actions), but for monitoring and placement discovery, it is complete.