PowerShell MCP
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
PowerShell MCP
A provider-neutral MCP server for bounded PowerShell execution on explicit local or registered SSH targets.
This is an independent project and is not affiliated with or endorsed by Microsoft.
Tools
list_powershell_targets()powershell_status(target)powershell_run(target, script, ...)
Targets are always explicit:
local
ssh:example-windowsThere is no implicit local fallback and arbitrary SSH destinations are rejected.
Related MCP server: cli-mcp
Install
Requires Python 3.11+, PowerShell (pwsh) for local execution, and OpenSSH for SSH targets.
pipx install .
claude mcp add --scope user --transport stdio powershell -- \
~/.local/bin/powershell-mcpFor development:
pipx install --editable .Configuration
The default target registry is ~/.config/powershell-mcp/targets.conf. Override it with POWERSHELL_MCP_REGISTRY.
example-windows | developer@example.invalid | powershell
forwarded | -p 2222 developer@127.0.0.1 | powershellThe registry is trusted configuration because its destination field is parsed as OpenSSH arguments. Keep it private and writable only by its owner.
Configure a pinned local runtime with POWERSHELL_MCP_PWSH; otherwise pwsh is resolved from PATH.
Examples
{"target":"local","script":"$PSVersionTable.PSVersion.ToString()"}{"target":"ssh:example-windows","script":"Get-Process","max_lines":20}Normal results contain only:
{"output":"...","exit_code":0}Failure, truncation, timeout, and raw protocol fields appear only when relevant. Raw records are opt-in with include_raw_records: true.
Bounds and security
This tool executes arbitrary PowerShell with the selected account's authority. It is not a sandbox.
targetis mandatory.SSH targets are allowlisted.
Line, byte, record, diagnostic, and time limits are enforced.
Process groups receive bounded TERM/KILL cleanup.
Exactly one terminal protocol record must be last.
Normal OpenSSH host-key verification is retained.
MCP approval generally applies to the tool, not individual target values.
Use least-privilege accounts and keep client-side tool approval enabled.
See configuration, protocol, security, and migration.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Scoped, audited SSH exec, sessions, and SFTP on your saved servers without exposing credentials
Scoped agent execution. Server-side credentials, policy, budgets and verifiable receipts.
Securely control computers you explicitly pair through files, terminals, processes, screenshots, desktop UI/input, clipboard, browser automation, diagnostics, and document tools.
Operate Linux, macOS and Windows from your LLM. Every action runs through an auditable allowlist.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables secure remote command execution and bidirectional file transfers on SSH servers through the Model Context Protocol. It features robust security controls including command whitelisting, credential isolation, and support for multiple SSH connection profiles.2,863 npm1,041ISC
- FlicenseNot gradedqualityDmaintenanceProvides secure execution of terminal commands (PowerShell, CMD, shell) with configurable security policies including command blocking, path restrictions, and timeout.1-
- FlicenseAqualityDmaintenanceEnables secure file system operations (read, write, delete) and simulated command execution with server-enforced permission policies, risk assessment, and human-in-the-loop approval.5-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to establish interactive-authenticated SSH sessions to explicitly configured targets, run and manage bounded background jobs, and transfer bounded UTF-8 text files over SFTP.MIT