svc-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SVC_HOST | Yes | SVC hostname or IP address (required) | |
| SVC_PORT | No | SVC SSH port (default: 22) | 22 |
| SVC_PASSWORD | No | SVC SSH password (for password authentication) | |
| SVC_USERNAME | No | SVC SSH username (default: superuser) | superuser |
| SVC_PROXY_HOST | No | SSH proxy hostname or IP address | |
| SVC_PROXY_PORT | No | SSH proxy port (default: 22) | 22 |
| SVC_PROXY_PASSWORD | No | SSH proxy password (for password authentication) | |
| SVC_PROXY_USERNAME | No | SSH proxy username | |
| SVC_PRIVATE_KEY_PATH | No | Path to SVC SSH private key (for key authentication) | |
| SVC_PROXY_PRIVATE_KEY_PATH | No | Path to SSH proxy private key (for key authentication) |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_system_statusC | Check SVC system status (lssystem) |
| execute_svc_commandC | Execute any SVC CLI command. This is a generic tool that allows you to run any SVC command directly. |
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 2 tools
The two tools have clearly distinct purposes: one checks overall system status, and the other executes arbitrary SVC commands. There is no ambiguity between them.
Both tools use a verb_noun pattern (check_system_status, execute_svc_command) which is consistent. Minor deviation is that the noun phrases are of different lengths, but it's still readable.
With only 2 tools, the server feels underdeveloped for any practical SVC management use case. While a check + generic execute pattern can work in principle, it suggests the tool surface is very thin.
The generic execute_svc_command tool compensates for missing specific operations, but the server lacks dedicated tools for common tasks like listing volumes, managing hosts, or creating storage pools. The set is not complete for typical SVC administration workflows.