Click on "Install 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., "@Auralis Commanderstart npm run dev and show me the output"
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.
Auralis Commander
The lightweight Windows MCP server that does more with less.
Why Auralis Commander?
We built Auralis Commander because existing solutions were either too heavy or too limited:
MCP Server | Tools | Focus | Problem |
Desktop Commander | 26 | Everything | Bloated, 5 tools just for processes |
Filesystem (Anthropic) | 11 | Files only | No shell, no processes, no system info |
Windows CLI | 8 | PowerShell | No file operations, limited scope |
Auralis Commander: 14 tools that cover shell, files, search, processes, and system ā without the bloat.
Key Advantages
šÆ Smart Design
One process_interactive tool replaces 5 separate tools in Desktop Commander:
start_processāprocess_interactive { action: "start" }read_process_outputāprocess_interactive { action: "read" }interact_with_processāprocess_interactive { action: "write" }force_terminateāprocess_interactive { action: "kill" }list_sessionsāprocess_interactive { action: "list" }
š¦ Batch Operations
Read multiple files in one call:
ā” Windows-Native
Optimized for PowerShell and Windows workflows. No WSL required, no Unix assumptions.
šŖ¶ Lightweight
~14KB of focused code. Fast startup, minimal memory footprint, smaller context window usage.
Tool Comparison
Capability | Auralis | Desktop Commander | Filesystem | Windows CLI |
Shell execution | ā | ā | ā | ā |
File read/write | ā | ā | ā | ā |
File search | ā | ā | ā | ā |
Batch file read | ā | ā | ā | ā |
Interactive processes | ā | ā | ā | ā |
Process management | ā | ā | ā | ā |
System info | ā | ā | ā | ā |
Find & replace | ā | ā | ā | ā |
Total tools | 14 | 26 | 11 | 8 |
Context overhead | Low | High | Low | Low |
Installation
Option 1: npm (recommended)
Option 2: Clone and Build
Claude Desktop Configuration
Add to your claude_desktop_config.json:
Windows: %APPDATA%\Claude\claude_desktop_config.json
Restart Claude Desktop to load the server.
Tools Reference
Shell & System
Tool | Description |
| Execute commands in pwsh, powershell, or cmd |
| Get CPU, memory, disk usage, and uptime |
| List running processes with memory/CPU stats |
| Terminate process by PID or name |
| Run and interact with long-running processes |
Files
Tool | Description |
| Read single file or batch with |
| Write or append to file, auto-create directories |
| Find and replace text in files |
| Delete files or directories (with |
| Move or rename files and directories |
| Get metadata: size, dates, line count, permissions |
Directories & Search
Tool | Description |
| List contents with depth control and glob patterns |
| Create directory with parent directories |
| Search by filename or content with filtering |
Usage Examples
Run a Dev Server
Interactive Python REPL
Batch Configuration Check
Quick System Health Check
Configuration
Create auralis-commander.json in your home directory for defaults:
Option | Default | Description |
|
| Shell for commands: |
| Home dir | Default working directory |
|
| Maximum file size for reading |
Architecture
Contributing
Issues and PRs welcome. Please:
Keep tools focused ā no feature creep
Maintain Windows compatibility
Test with Claude Desktop before submitting
License
MIT License ā use it, modify it, ship it.