Skip to main content
Glama
posidron

PowerShell MCP Server

by posidron

execute_ps

Execute PowerShell commands directly on Windows systems. Use the tool to run scripts, manage modules, and retrieve system information efficiently via the PowerShell MCP Server.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
commandYesPowerShell command to execute

Implementation Reference

  • Handler function that executes the provided PowerShell command using Node.js child_process execAsync. Escapes double quotes in the command, captures stdout and stderr, and returns formatted text content or error response.
    async ({ command }: { command: string }) => {
      try {
        const { stdout, stderr } = await execAsync(
          `powershell -Command "${command.replace(/"/g, '\\"')}"`
        );
    
        if (stderr) {
          return {
            isError: true,
            content: [
              {
                type: 'text' as const,
                text: `Error executing PowerShell command: ${stderr}`,
              },
            ],
          };
        }
    
        return {
          content: [
            {
              type: 'text' as const,
              text: stdout,
            },
          ],
        };
      } catch (error) {
        return {
          isError: true,
          content: [
            {
              type: 'text' as const,
              text: `Error executing PowerShell command: ${(error as Error).message}`,
            },
          ],
        };
      }
    }
  • Zod schema defining the input parameter 'command' as a string for the execute_ps tool.
    {
      command: z.string().describe('PowerShell command to execute'),
    },
  • src/index.ts:34-77 (registration)
    Registration of the 'execute_ps' tool with the MCP server using this.server.tool, including inline schema and handler.
    this.server.tool(
      'execute_ps',
      {
        command: z.string().describe('PowerShell command to execute'),
      },
      async ({ command }: { command: string }) => {
        try {
          const { stdout, stderr } = await execAsync(
            `powershell -Command "${command.replace(/"/g, '\\"')}"`
          );
    
          if (stderr) {
            return {
              isError: true,
              content: [
                {
                  type: 'text' as const,
                  text: `Error executing PowerShell command: ${stderr}`,
                },
              ],
            };
          }
    
          return {
            content: [
              {
                type: 'text' as const,
                text: stdout,
              },
            ],
          };
        } catch (error) {
          return {
            isError: true,
            content: [
              {
                type: 'text' as const,
                text: `Error executing PowerShell command: ${(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