pwsh-exec
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PWSH_EXEC_DEFAULT_DIR | No | Default working directory for commands. If not set, falls back to %TEMP%\pwsh-exec |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_commandA | Execute a command in a new PowerShell (pwsh 7) process. Stateless — no state persists between calls. NOT for long-running tasks. Hard cap is 300 seconds (5 minutes); there is no background mode. Do NOT use for: installers (Ollama, VS, .NET SDK, etc.), large builds, package managers that may exceed 5 minutes (npm install on cold cache, pip install torch, etc.), dev servers, or anything interactive. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no risk of confusion or overlap. The single tool has a clear, distinct purpose.
The single tool name 'run_command' follows a clear verb_noun pattern, consistent with itself.
One tool is minimal but appropriately scoped for executing commands in a stateless manner. The server's purpose is narrow, so the tool count fits well.
The tool covers the core functionality of running commands. While features like background execution or state management are missing, they are explicitly excluded, so the surface is complete for its intended use.