- Home
- MCP servers
- Quiet Shell
Quiet Shell
- typescript
3
GitHub Stars
typescript
Language
6 months ago
First Indexed
2 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
Configuration
View docs{
"mcpServers": {
"mrsimpson-quiet-shell-mcp": {
"command": "quiet-shell-mcp",
"args": []
}
}
}quiet-shell is an MCP server that runs shell commands and filters the output to show only the most useful lines, such as errors and summaries. By reducing noisy output, it helps you focus on actionable feedback when you’re orchestrating builds, tests, or scripts through an AI-enabled workflow.
How to use
To use quiet-shell with an MCP client, start the MCP server as a local stdio transport. Your client will send commands to the server and receive structured responses that include a concise, filtered output along with the final status.
How to install
Prerequisites you need before installation:
- Node.js 18 or newer must be installed on your system
- npm or pnpm should be available for installation
- Git may be useful for cloning repositories if you prefer a source install
# Install globally with npm
npm install -g @codemcp/quiet-shell-mcp
# Or install globally with pnpm
pnpm add -g @codemcp/quiet-shell-mcp
Configuration and getting started
Configure your MCP client to connect to the quiet-shell MCP server via stdio. You can run the server locally and point your client at the provided executable.
# Claude Desktop example configuration (local MCP server via stdio)
{
"mcpServers": {
"quiet-shell": {
"command": "quiet-shell-mcp"
}
}
}
Additional setup for other clients
If you are using an MCP client other than Claude Desktop, you can invoke the server with the same command shown above. The server communicates via stdio following the Model Context Protocol specification.
Notes and behavior
When you execute commands, quiet-shell analyzes the output and returns a filtered snippet that highlights errors, failures, and a concise summary. You can adjust how output is shown by selecting appropriate templates, or define custom templates in your repository.
Examples of common usage patterns
- Run tests with focused output using a built-in template that surfaces failures and a summary. - Compile code to surface type or syntax errors only. - Render complete output when needed by overriding the default suppression.
Available tools
execute_command
Runs a shell command through the MCP server and returns filtered output, status, and the template used.
list_templates
Lists available output-filtering templates with descriptions and settings.