Skip to main content
Glama
posidron

PowerShell MCP Server

by posidron

run_script

Execute PowerShell scripts on Windows systems through the PowerShell MCP Server by specifying the script path and optional parameters for automation and system management tasks.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
parametersNoOptional parameters to pass to the script
scriptPathYesPath to the PowerShell script file

Implementation Reference

  • The asynchronous handler function for the 'run_script' tool. It constructs a PowerShell command to execute the script file with optional parameters using execAsync, handles stdout/stderr, and returns formatted content or error response.
    async ({ scriptPath, parameters }: { scriptPath: string; parameters?: string }) => {
      try {
        const fullCommand = parameters
          ? `powershell -File "${scriptPath}" ${parameters}`
          : `powershell -File "${scriptPath}"`;
    
        const { stdout, stderr } = await execAsync(fullCommand);
    
        if (stderr) {
          return {
            isError: true,
            content: [
              {
                type: 'text' as const,
                text: `Error running script: ${stderr}`,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text' as const,
              text: stdout || 'Script executed successfully with no output.',
            },
          ],
        };
      } catch (error) {
        return {
          isError: true,
          content: [
            {
              type: 'text' as const,
              text: `Error running script: ${(error as Error).message}`,
            },
          ],
        };
      }
  • Zod input schema defining 'scriptPath' as required string (path to PS script) and 'parameters' as optional string.
    {
      scriptPath: z.string().describe('Path to the PowerShell script file'),
      parameters: z.string().optional().describe('Optional parameters to pass to the script'),
  • src/index.ts:313-359 (registration)
    Registration of the 'run_script' tool on the MCP server using this.server.tool(), specifying the name, input schema, and handler function.
    this.server.tool(
      'run_script',
      {
        scriptPath: z.string().describe('Path to the PowerShell script file'),
        parameters: z.string().optional().describe('Optional parameters to pass to the script'),
      },
      async ({ scriptPath, parameters }: { scriptPath: string; parameters?: string }) => {
        try {
          const fullCommand = parameters
            ? `powershell -File "${scriptPath}" ${parameters}`
            : `powershell -File "${scriptPath}"`;
    
          const { stdout, stderr } = await execAsync(fullCommand);
    
          if (stderr) {
            return {
              isError: true,
              content: [
                {
                  type: 'text' as const,
                  text: `Error running script: ${stderr}`,
                },
              ],
            };
          }
    
          return {
            content: [
              {
                type: 'text' as const,
                text: stdout || 'Script executed successfully with no output.',
              },
            ],
          };
        } catch (error) {
          return {
            isError: true,
            content: [
              {
                type: 'text' as const,
                text: `Error running script: ${(error as Error).message}`,
              },
            ],
          };
        }
      }
    );
Behavior1/5

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

Tool has no description.

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

Conciseness1/5

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

Tool has no description.

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

Completeness1/5

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

Tool has no description.

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

Parameters1/5

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

Tool has no description.

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

Purpose1/5

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

Tool has no description.

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

Usage Guidelines1/5

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

Tool has no description.

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

Install Server

Other Tools

Related Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/posidron/mcp-powershell'

If you have feedback or need assistance with the MCP directory API, please join our Discord server