Experimental MCP server to execute command line commands
Experimental MCP server to execute command line commands. The cmd mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.
The server implements one tool: - run_command: Runs a command line comment - Takes "cmd" and "args" as string arguments - Runs the command and returns stdout, stderr, status_code, etc.
Everything the assistant can do here goes through one of these:
run_command — Runs a command line commentTools — The server implements one tool: - run_command: Runs a command line comment - Takes "cmd" and "args" as string arguments - Runs the command andDebugging — Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCPYou will need one environment variable: UV_PUBLISH_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.
Installation goes through your MCP client rather than a global install: point it at @modelcontextprotocol/inspector on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Cmd's toolset — run_command, Tools, Debugging — is a fair guide to whether it matches your workflow. It is maintained by MarkusPfundstein; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| run_command | Runs a command line comment |
| Tools | The server implements one tool: - run_command: Runs a command line comment - Takes "cmd" and "args" as string arguments - Runs the command and returns stdout, stderr, status_code, etc. |
| Debugging | Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector). |
"mcpServers": {
"cmd-line-executor": {
"command": "uv",
"args": [
"--directory",
"/Users/$(whoami)/experiments/claude-mvp/cmd-line-executor",
"run",
"cmd-line-executor"
]
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| UV_PUBLISH_TOKEN | Credential the server authenticates with. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.