Skip to main content
Glama
enesjakozh
deepsuthar496

Remote Command MCP Server

by deepsuthar496
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Hybrid

远程命令 MCP 服务器

一个模型上下文协议 (MCP) 服务器，支持跨不同操作系统执行远程命令。该服务器提供统一的接口来执行 Shell 命令，自动处理 Windows 和类 Unix 系统之间的平台特定差异。

特征

  • 跨平台命令执行

  • Windows 和 Unix 之间的自动命令规范化

  • 内置错误处理和输出流

  • 工作目录规范支持

  • 特定于平台的 shell 选择

Related MCP server: MCP Shell Server

安装

  1. 克隆存储库：

git clone https://github.com/deepsuthar496/Remote-Command-MCP
cd remote-command-server

  1. 安装依赖项：

npm install

  1. 构建服务器：

npm run build

  1. 在您的设置文件中配置 MCP 服务器：

对于 VSCode Cline 扩展（ cline_mcp_settings.json ）：

{
  "mcpServers": {
    "remote-command": {
      "command": "node",
      "args": ["path/to/remote-command-server/build/index.js"],
      "disabled": false,
      "autoApprove": []
    }
  }
}

用法

该服务器提供了一个名为execute_remote_command的工具，它可以在主机上执行任何有效的shell命令。其中包括：

  • 系统命令

  • 包管理器命令（apt、yum、chocolatey 等）

  • 开发工具（git、npm、python等）

  • 文件操作

  • 网络命令

  • 服务管理

  • 以及系统上可用的任何其他 CLI 命令

工具：execute_remote_command

参数：

  • command （必需）：可以在主机操作系统上执行的任何有效 shell 命令

  • cwd （可选）：命令执行的工作目录

示例

  1. 系统信息：

<use_mcp_tool>
<server_name>remote-command</server_name>
<tool_name>execute_remote_command</tool_name>
<arguments>
{
  "command": "systeminfo"  // Windows
  // or "uname -a"        // Linux
}
</arguments>
</use_mcp_tool>

  1. 包管理：

<use_mcp_tool>
<server_name>remote-command</server_name>
<tool_name>execute_remote_command</tool_name>
<arguments>
{
  "command": "npm list -g --depth=0"  // List global NPM packages
}
</arguments>
</use_mcp_tool>

  1. 网络运营：

<use_mcp_tool>
<server_name>remote-command</server_name>
<tool_name>execute_remote_command</tool_name>
<arguments>
{
  "command": "netstat -an"  // Show all network connections
}
</arguments>
</use_mcp_tool>

  1. Git操作：

<use_mcp_tool>
<server_name>remote-command</server_name>
<tool_name>execute_remote_command</tool_name>
<arguments>
{
  "command": "git status",
  "cwd": "/path/to/repo"
}
</arguments>
</use_mcp_tool>

  1. 文件操作：

<use_mcp_tool>
<server_name>remote-command</server_name>
<tool_name>execute_remote_command</tool_name>
<arguments>
{
  "command": "ls -la",  // List files with details
  "cwd": "/path/to/directory"
}
</arguments>
</use_mcp_tool>

  1. 流程管理：

<use_mcp_tool>
<server_name>remote-command</server_name>
<tool_name>execute_remote_command</tool_name>
<arguments>
{
  "command": "ps aux"  // List all running processes (Unix)
  // or "tasklist"     // Windows equivalent
}
</arguments>
</use_mcp_tool>

  1. 服务控制：

<use_mcp_tool>
<server_name>remote-command</server_name>
<tool_name>execute_remote_command</tool_name>
<arguments>
{
  "command": "systemctl status nginx"  // Check service status (Linux)
  // or "sc query nginx"               // Windows equivalent
}
</arguments>
</use_mcp_tool>

安全注意事项

由于此服务器可以执行任何系统命令，请考虑以下安全措施：

  1. 访问控制：仅限受信任的用户访问 MCP 服务器

  2. 命令验证：在应用程序逻辑中执行命令之前验证命令

  3. 工作目录：使用cwd参数将命令执行限制在特定目录中

  4. 环境：谨慎使用修改系统设置或敏感文件的命令

  5. 权限：使用适当的用户权限运行 MCP 服务器

跨平台命令处理

服务器自动处理特定于平台的差异：

  1. 命令翻译：

    • ls ⟷ dir (根据平台自动转换)

    • 适合每个平台的正确管道运算符格式

  2. 外壳选择：

    • Windows：使用cmd.exe

    • Unix/Linux：使用/bin/sh

错误处理

服务器提供详细的错误消息，并在响应中包含 stdout 和 stderr。如果命令失败，您将收到一条错误消息，其中包含有关错误的详细信息。

错误响应示例：

{
  "content": [
    {
      "type": "text",
      "text": "Command execution error: Command failed with exit code 1"
    }
  ],
  "isError": true
}

发展

项目结构

remote-command-server/
├── src/
│   └── index.ts    # Main server implementation
├── package.json
├── tsconfig.json
└── README.md

建筑

npm run build

这将编译 TypeScript 代码并在build目录中创建可执行文件。

贡献

  1. 分叉存储库

  2. 创建你的功能分支（ git checkout -b feature/amazing-feature ）

  3. 提交您的更改（ git commit -m 'Add some amazing feature' ）

  4. 推送到分支（ git push origin feature/amazing-feature ）

  5. 打开拉取请求

执照

该项目根据 MIT 许可证获得许可 - 有关详细信息，请参阅 LICENSE 文件。

Available Tools

1 tool
execute_remote_commandC

Execute a command on the host machine

ParametersJSON Schema
NameRequiredDescriptionDefault
commandYesCommand to execute
cwdNoWorking directory for command execution

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries full burden for behavioral disclosure. It mentions execution but doesn't describe permissions required, whether commands run asynchronously, timeout behavior, error handling, or output format. For a potentially dangerous remote execution tool, this is a significant gap.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, efficient sentence that states the core functionality without unnecessary words. It's appropriately sized and front-loaded with the essential information.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool that executes remote commands with no annotations and no output schema, the description is insufficient. It doesn't address critical aspects like security implications, execution environment, error conditions, or what the tool returns. The combination of high-risk functionality and minimal description creates significant gaps.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema already documents both parameters (command and cwd) adequately. The description doesn't add any additional meaning about parameter usage beyond what's in the schema, meeting the baseline for high schema coverage.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('execute') and target ('command on the host machine'), providing a specific verb+resource combination. It doesn't need to differentiate from siblings since none exist, but it could be more specific about what types of commands or hosts are supported.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus alternatives or what prerequisites might be needed. The description states what it does but offers no context about appropriate use cases, security considerations, or limitations.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool update
    • First observedexecute_remote_command
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or confusion between tools. The tool's purpose is singular and clearly defined.

Naming Consistency5/5

Since there is only one tool, it inherently maintains consistency. The naming follows a clear verb_noun pattern (execute_remote_command).

Tool Count2/5

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.

Completeness1/5

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.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Shell MCP Server

    odysseus0
    A
    license
    Not graded
    quality
    D
    maintenance
    A Model Context Protocol server that allows LLMs to execute shell commands and receive their output in a controlled manner.
    7
    MIT

  • SSH MCP Server

    mfangtao
    A
    license
    B
    quality
    D
    maintenance
    A server that enables remote command execution over SSH through the Model Context Protocol (MCP), supporting both password and private key authentication.
    1
    1
    2
    MIT

  • SSH MCP Server

    vilasone455
    F
    license
    A
    quality
    D
    maintenance
    A local Model Context Protocol server that allows LLMs to securely execute shell commands on remote Linux and Windows systems via SSH connections.
    6
    17
    2
    -

Appeared in Searches

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/deepsuthar496/Remote-Command-MCP'

If you have feedback or need assistance with the MCP directory API, please join our Discord server