MCP PowerShell Exec Server

Created By
dfinkea year ago
MCP Server for executing PowerShell scripts
Overview

What is MCP PowerShell Exec Server?

MCP PowerShell Exec Server is a lightweight server designed to accept and execute PowerShell scripts, enabling AI assistants to interact with PowerShell seamlessly.

How to use MCP PowerShell Exec Server?

To use the server, clone the repository, set it up, and integrate it with GitHub Copilot in VSCode Insiders by configuring the server settings in the .vscode/mcp.json file.

Key features of MCP PowerShell Exec Server?

  • Accepts PowerShell scripts as string inputs.
  • Executes scripts securely in an MCP Server environment.
  • Returns execution results in real-time.

Use cases of MCP PowerShell Exec Server?

  1. Automating system administration tasks using PowerShell scripts.
  2. Enhancing AI assistants with the ability to execute PowerShell commands.
  3. Integrating with development environments for real-time script execution.

FAQ from MCP PowerShell Exec Server?

  • What are the system requirements?

Python 3.10 or higher and PowerShell 5.1 are required for optimal performance.

  • Is there a license for this project?

Yes, it is licensed under the MIT License.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
dfinke
Star
1
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

10 minutes ago