cmd-mcp-server
The cmd-mcp-server is a Model Context Protocol (MCP) server that enables command-line operations on both local and remote systems:
Local command execution: Run shell commands on the host machine with options to persist or create new shell sessions
Remote execution via SSH: Connect to remote servers using hostname, username, and password/private key authentication
SSH configuration options: Specify custom ports (default: 22) and choose between persistent or new SSH sessions
Cross-platform compatibility: Works on both Windows and Linux systems
Integration capabilities: Built on the MCP SDK for compatibility with other MCP applications
TypeScript implementation: Provides enhanced type safety and development experience
Allows the execution of command-line operations on Linux systems through a persistent shell session, providing access to Linux system commands and utilities.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@cmd-mcp-server list all files in the current directory"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
CMD MCP Server
A Model Context Protocol (MCP) server implementation for executing CMD commands on both Windows and Linux, as well as allowing SSH connections. This server allows you to integrate command-line operations with MCP-compatible applications.
Features
Execute CMD commands through MCP
TypeScript implementation
Built on the official MCP SDK
Cross-platform compatibility
Related MCP server: Globalping
Installation
Installing via Smithery
To install CMD Server for Claude Desktop automatically via Smithery:
npx -y @smithery/cli install server-cmd --client claudeManual Installation
npm install server-cmdPrerequisites
Node.js (v16 or higher recommended)
npm or yarn package manager
Usage
import { MCPCmdServer } from 'server-cmd';
// Initialize the server
const server = new MCPCmdServer();
// Start the server
server.start();Configuration
The server can be configured through environment variables or a configuration object:
const config = {
// Add your configuration options here
};
const server = new MCPCmdServer(config);Development
To set up the development environment:
Clone the repository:
git clone https://github.com/PhialsBasement/CMD-MCP-Server.git
cd CMD-MCP-ServerInstall dependencies:
npm installBuild the project:
npm run buildScripts
npm run build- Compile TypeScript to JavaScriptnpm run prepare- Prepare the package for publishing
Dependencies
@modelcontextprotocol/sdk: ^1.0.1glob: ^10.3.10zod-to-json-schema: ^3.23.5
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
License
This project is licensed under the MIT License - see the LICENSE file for details.
Security
Please note that executing command-line operations can be potentially dangerous. Make sure to implement proper security measures and input validation when using this server in production environments.
Support
For issues and feature requests, please use the GitHub issue tracker.
Available Tools
2 toolsexecute_commandA
Execute a command and return its output. Commands run in a persistent shell session by default. Use newSession: true to run in a new shell instance.
Inputs: command (required), newSession.
execute_ssh_commandC
Execute a command on a remote server via SSH. Commands run in a persistent SSH session by default. Use newSession: true to run in a new session.
Inputs: host (required), username (required), command (required), port, +3 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: execute_command handles local shell commands, while execute_ssh_command handles remote SSH commands. There is no overlap or ambiguity between them, as each targets a different execution environment.
Both tools follow a consistent verb_noun pattern with 'execute_' as the prefix and descriptive suffixes ('command' and 'ssh_command'). The naming is perfectly uniform and predictable across the tool set.
With only 2 tools, the server feels thin for a command execution domain. It lacks essential operations like listing available commands, managing sessions, or handling file operations, which are common in such contexts. The count is too low for adequate coverage.
The tool set is severely incomplete for command execution. It covers basic local and remote command execution but misses critical functionalities such as session management tools, command history, file transfer, or environment configuration, leaving significant gaps for agent workflows.
Maintenance
Related MCP Connectors
A simple MCP server built with FastMCP and python
Related MCP Servers
- MIT

Globalpingofficial
FlicenseNot gradedqualityBmaintenanceRemote MCP server that gives LLMs access to run network commands66-- AlicenseNot gradedqualityDmaintenanceMCP server exposing pwntools 4.15.0 functionality for binary exploitation tasks.29 PyPI2MIT
- FlicenseNot gradedqualityDmaintenanceMCP server providing filesystem operations, shell execution, and web search capabilities.-