mcp-server-commands
- OS Automation
- Developer Tools
An MCP server to run commands.
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| run_command | Include command output in the prompt. Instead of a tool call, the user decides what commands are relevant. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_command | |
| run_script |
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
mcp-server-commands
An MCP server to run commands.
Published to npm as mcp-server-commands using this workflow
[!WARNING] Be careful what you ask this server to run! In Claude Desktop app, use
Approve Once(notAllow for This Chat) so you can review each command, useDenyif you don't trust the command. Permissions are dictated by the user that runs the server. DO NOT run withsudo.
Tools
Tools are for LLMs to request, i.e. Claude Desktop app. Claude Sonnet 3.5 intelligently uses both tools, I was pleasantly surprised.
run_command- run a command, i.e.hostnameorls -alorecho "hello world"etc- Returns STDOUT and STDERR as text
run_script- run a script! (i.e.fish,bash,zsh,python)- Let your LLM run the code it writes!
- script is passed over STDIN
run_script==run_command+ script over STDIN- Claude has been pretty creative with this, i.e. using
catas the interpreter to create new files!
Prompts
Prompts are for users to include in chat history, i.e. via Zed's slash commands (in its AI Chat panel)
run_command- generate a prompt message with the command output
Development
Install dependencies:
Build the server:
For development with auto-rebuild:
Installation
To use with Claude Desktop, add the server config:
On MacOS: ~/Library/Application Support/Claude/claude_desktop_config.json
On Windows: %APPDATA%/Claude/claude_desktop_config.json
Use the published npm package
Use a local build (repo checkout)
Logging
Claude Desktop app writes logs to ~/Library/Logs/Claude/mcp-server-mcp-server-commands.log
By default, only important messages are logged (i.e. errors).
If you want to see more messages, add --verbose to the args when configuring the server.
By the way, logs are written to STDERR because that is what Claude Desktop routes to the log files.
In the future, I expect well formatted log messages to be written over the STDIO transport to the MCP client (note: not Claude Desktop app).
Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the MCP Inspector, which is available as a package script:
The Inspector will provide a URL to access debugging tools in your browser.
GitHub Badge
Glama performs regular codebase and documentation scans to:
- Confirm that the MCP server is working as expected.
- Confirm that there are no obvious security issues with dependencies of the server.
- Extract server characteristics such as tools, resources, prompts, and required parameters.
Our directory badge helps users to quickly asses that the MCP server is safe, server capabilities, and instructions for installing the server.
Copy the following code to your README.md file: