Remote Command MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| execute_remote_commandC | Execute a command on the host machine |
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 1 tool
With only one tool, there is no possibility of ambiguity or confusion between tools. The tool's purpose is singular and clearly defined.
Since there is only one tool, it inherently maintains consistency. The naming follows a clear verb_noun pattern (execute_remote_command).
A single tool is too few for a server named 'Remote Command MCP Server', which suggests a broader scope for remote command execution. This minimal set limits functionality and may cause agent failures due to lack of supporting operations.
The tool surface is severely incomplete. It only provides command execution with no support for listing available commands, checking command status, handling outputs, or managing remote sessions, which are essential for the domain.