Windows Developer MCP Server

by peeyushcodes

Overview Schema Source Related Servers Discussions Admin

Python

Local

run_powershell

Run PowerShell commands and capture output, with automatic security blocking of dangerous operations.

Instructions

Execute a PowerShell command and return the output.

The command passes through the full security validation pipeline before execution. Dangerous commands (format, shutdown, etc.) are blocked automatically.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "command": "<command>"
    },
    "name": "run_powershell"
  }
}

Input Schema

Name	Required	Description	Default
`command`	Yes	The PowerShell command or expression to execute.
`timeout`	No	Maximum execution time in seconds (1–3600). Default: 60.

Output Schema

Name	Required	Description	Default
No arguments

Schema Changelog

Changes observed during successful MCP inspections.

First observedv0.1.0Aug 3, 2026

TDQS

A3.8/5.0

Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description must carry the behavioral disclosure. It does mention the security validation pipeline and automatic blocking of dangerous commands, which is valuable. However, it omits side-effect risks, error behavior, and environment assumptions, so transparency is partial.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is two crisp sentences. The first sentence provides immediate actionable information, and the second adds essential security context without redundancy. Every word earns its place.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple two-parameter command executor, the description is reasonably complete: it covers purpose, output, and safety behavior. The presence of an output schema handles return-value details. It falls slightly short on explicitly describing when to prefer this over sibling tools, but that is minor.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema covers both parameters (command and timeout) with descriptions, so schema coverage is 100%. The tool description adds no extra parameter details, keeping the score at the baseline 3.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states 'Execute a PowerShell command and return the output,' specifying the exact shell and expected outcome. This distinguishes it from sibling tools like run_cmd (CMD) and run_python_script (Python), though it doesn't explicitly name them.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description gives no explicit guidance on when to use this tool versus alternatives such as run_cmd or run_script. The usage is implied by the tool name and the stated purpose, but there are no when/when-not criteria or alternative references.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server