Skip to main content
Glama
danielklecha

mcp-server-for-powershell

by danielklecha
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
cwdNoInitial working directory.Current Directory
language-modeNoPowerShell Language Mode: 0 (NoLanguage), 1 (ConstrainedLanguage), 2 (RestrictedLanguage), 3 (FullLanguage).1
allowed-commandsNoList of allowed PowerShell commands. If empty, all are allowed (subject to restrictions).[]
restricted-commandsNoList of restricted PowerShell commands.Safe defaults
restricted-directoriesNoList of restricted directories.System directories

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
run_powershellA
Executes PowerShell commands based on a structured JSON definition.

This tool allows you to run PowerShell commands safely strings.
It expects a JSON string that defines the command(s), parameters, pipelines, and sequences.

Args:
    json: A JSON string defining the command structure.
          Structure examples:
          1. Single Command:
             [{"command": "Get-Item", "parameters": ["."]}]

          2. .NET Static Method:
             [{"command": "[System.Math]::Sqrt", "parameters": [16]}]
             # Generates: [System.Math]::Sqrt(16)

          3. Command with Named Parameters:
             [{"command": "Get-Item", "parameters": {"-Path": "."}}]

          4. Pipeline:
             [{"command": "Get-Process", "then": {"command": "Select-Object", "parameters": ["Name"]}}]

          5. Sequence (Multiple commands):
             [{"command": "mkdir", "parameters": ["test"]}, {"command": "cd", "parameters": ["test"]}]

Returns:
    The standard output of the executed PowerShell command(s), or an error message if execution fails.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap. The agent can uniquely identify the tool's purpose without ambiguity.

Naming Consistency5/5

The single tool name follows a clear verb_noun pattern (run_powershell), which is consistent and readable. Since there's only one tool, no convention conflicts exist.

Tool Count3/5

The server has only one tool for the broad domain of PowerShell execution. While the tool is versatile, it forces the agent to encode all operations as complex JSON, which is less ergonomic than dedicated tools for common tasks. The count is borderline.

Completeness4/5

The single tool can theoretically execute any PowerShell command, covering the domain of command execution comprehensively. However, it lacks specialized tools for session management, script handling, or error recovery, which may be needed for complex workflows.

Maintenance

ActivityNo data
ResponsivenessNo issues

Resources