Provides process and service management capabilities for Docker services running on Windows, including discovery, monitoring, and control of Docker Desktop Service and related processes
Enables management and monitoring of Node.js processes, including port-based discovery, process termination, and resource analysis for Node.js development servers and applications
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PortMaster MCPwhat's running on port 8080?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PortMaster MCP
Overview
PortMaster MCP is a comprehensive Windows process and service management tool that provides both AI-assisted and direct command-line interfaces. It enables secure discovery, inspection, and control of any Windows service or process by name, PID, or port number with integrated UAC elevation.
π Dual Interface Design
π€ Claude Code Integration: Full MCP server for AI-assisted process management
β‘ Standalone CLI: Direct PowerShell interface via
portmaster-cli.ps1π Unified Security: Consistent UAC elevation across both interfaces
Key Features
π Discovery & Inspection
Find processes by service name (supports wildcards)
Find processes listening on specific ports or port ranges
Get detailed process information by single or multiple PIDs
List all listening ports on the system
Analyze complete process trees with parent/child relationships
Network connection analysis (listening ports + active connections)
Process chain visualization with memory and resource usage
π οΈ Management Capabilities
Kill individual processes by PID
Kill multiple processes at once
Kill all processes using specific ports
Start, stop, and restart Windows services
UAC elevation for admin operations (no need to run Claude Code as admin)
π Security Features
UAC Elevation: Only prompts for admin privileges when needed
Confirmation Required: All destructive operations require explicit confirmation
Safe Defaults: Read-only operations work without elevation
Process Tree Analysis: Shows impact before performing operations
Installation
Prerequisites
Windows OS (Windows 10/11 or Windows Server)
Python 3.8+
PowerShell (pre-installed on Windows)
Claude Code installed
Quick Setup (Recommended)
Option A: Automatic Setup
# Install dependencies and configure automatically
pip install -r requirements.txt
python portmaster_mcp_setup.pyThe setup script will:
β Check dependencies and PowerShell policy
β Automatically add MCP server to your Claude config
β Create backup of existing config
β Show next steps
Option B: Manual Setup
1. Install Python Dependencies
pip install -r requirements.txt2. Configure PowerShell Execution Policy
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser3. Add to Claude Code Settings
Add this configuration to your Claude Code settings file (%USERPROFILE%\.claude.json):
{
"mcpServers": {
"portmaster_mcp": {
"type": "stdio",
"command": "python",
"args": [
"C:\\path\\to\\your\\portmaster_mcp\\portmaster_mcp.py"
],
"env": {}
}
}
}Replace the path with your actual installation directory.
4. Restart Claude Code
Close and restart Claude Code to load the new MCP server.
Standalone CLI Usage
For direct command-line access without Claude Code, use the included portmaster-cli.ps1 script:
π Quick Start
Option 1: Automated Setup (Recommended)
# Clone and setup in one go
git clone <repository-url> portmaster_mcp
cd portmaster_mcp
pip install -r requirements.txt
python portmaster_mcp_setup.pyOption 2: Quick CLI Examples
# Check what's running on development ports
.\portmaster-cli.ps1 check-ports 3000-3005
# Check specific ports
.\portmaster-cli.ps1 check-ports 443,8080,8443
# Find services with wildcards
.\portmaster-cli.ps1 find-service "*Docker*"
# Get detailed process info with full chain analysis
.\portmaster-cli.ps1 process-info 1234
# Kill processes on specific ports (requires admin)
.\portmaster-cli.ps1 kill-port 8080 -Force
# Show all available commands
.\portmaster-cli.ps1 helpπ CLI Commands Reference
Command | Description | Admin Required | Example |
| Check what's listening on ports | β |
|
| Show all listening ports | β |
|
| Find services by pattern | β |
|
| Get service details | β |
|
| Comprehensive process analysis | β |
|
| Terminate specific process | β |
|
| Kill processes using ports | β |
|
| Kill multiple processes | β |
|
| Stop Windows service | β |
|
| Start Windows service | β |
|
| Restart Windows service | β |
|
Claude Code Usage Examples
Service Management
"Find processes for services matching SQL*"
"Find processes for WindowsTestService"
"Find processes for *Web*"
"Stop service W3SVC"
"Start service MSSQLSERVER"
"Restart service Docker Desktop Service"Port-Based Discovery
"What process is listening on port 80?"
"Find processes on ports 443, 8080, and 3000"
"Kill all processes using port 8080"Process Management
"Get detailed information about process 1234"
"Get information about multiple processes 1234, 5678, 9012"
"Kill process 5678"
"Kill processes 1234, 5678, 9012"
"Show me all listening ports"Multiple Process Analysis
"Analyze processes 51008 and 30200 together"
"Compare resource usage for PIDs 1234, 5678, 9012"
"Show network connections for processes 51008, 30200"
"Get detailed chain info for multiple Node.js processes"Advanced Operations
"Find all IIS-related services and their ports"
"Stop all Node.js processes on development ports"
"Find which service is using port 443 and restart it"Available MCP Tools
Discovery Tools (No Admin Required)
Tool | Description | Example Usage |
| Find processes for any service pattern |
|
| Find processes on specific ports |
|
| List all listening ports |
|
| Get details for a PID |
|
| NEW: Get details for multiple PIDs |
|
| Get details for a service |
|
Management Tools (UAC Elevation Required)
Tool | Description | Security |
| Terminate a process by PID | UAC + Confirmation |
| Kill all processes on port(s) | UAC + Confirmation |
| Kill multiple processes by PIDs | UAC + Confirmation |
| Stop a Windows service | UAC + Confirmation |
| Start a Windows service | UAC |
| Restart a Windows service | UAC + Confirmation |
File Structure
portmaster_mcp/
βββ portmaster_mcp.py # Main MCP server with UAC elevation
βββ portmaster-cli.ps1 # Standalone CLI interface
βββ admin_helper.ps1 # PowerShell helper for elevated operations
βββ portmaster_mcp_setup.py # Automatic setup script
βββ requirements.txt # Python dependencies
βββ README.md # This documentationHow UAC Elevation Works
Normal Operations: Claude Code runs with standard user privileges
Admin Required: When you request a destructive operation (kill process, stop service)
UAC Prompt: Windows shows a UAC dialog asking for administrator approval
Elevated Execution: If approved, the operation runs with admin privileges in a separate session
Return to Normal: After completion, returns to standard privileges
This approach is more secure than running Claude Code as administrator constantly.
Troubleshooting
"Administrator privileges required"
This is normal for kill/service operations
Approve the UAC prompt when it appears
If UAC is disabled, you could run Claude Code as Administrator but I would advise to NOT do this.
"PowerShell execution policy error"
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUser"Module not found" errors
pip install mcp pydantic"Service not found"
Use wildcards:
*partial-name*Check exact service name:
Get-Servicein PowerShell
"Process not found"
Process may have already terminated
Check PID with Task Manager or
Get-Process
Getting Service Names
To find the exact names of Windows services:
Get-Service | Where-Object {$_.DisplayName -like "*keyword*"}Checking Port Usage
To see what's using ports:
netstat -ano | findstr :PORT_NUMBERSecurity Considerations
Safe Operations
Read operations never require elevation
Discovery tools are completely safe
UAC prompts appear only for destructive operations
Admin Operations
Always confirm before approving UAC prompts
Review the operation in the confirmation dialog
Cancel if you're unsure about the operation
Best Practices
Use discovery tools first to understand what you're managing
Review process trees before killing multiple processes
Prefer service operations over direct process killing when possible
Test on non-critical systems first
Example Workflows
Troubleshooting a Web Service
"Find processes for *Web*"- Discover web-related services"What's listening on port 80?"- Check if port is in use"Get info for service W3SVC"- Get IIS service details"Restart service W3SVC"- Restart if needed
Cleaning Up Development Processes
"Find processes on ports 3000, 8080, 9000"- Find dev servers"Kill processes using ports 3000, 8080"- Clean up dev ports"Show all listening ports"- Verify cleanup
CLI Alternative:
.\portmaster-cli.ps1 check-ports 3000-9000
.\portmaster-cli.ps1 kill-port 3000,8080 -Force
.\portmaster-cli.ps1 all-portsManaging Database Services
"Find services matching *SQL*"- Find database services"Stop service MSSQLSERVER"- Stop SQL Server"Start service MSSQLSERVER"- Start SQL Server
Analyzing Multiple Processes (NEW)
Comprehensive analysis of multiple processes at once:
Claude Code Examples:
"Analyze processes 51008 and 30200 together"
"Compare memory usage for Node.js processes 1234, 5678"
"Show network connections for multiple processes [51008, 30200]"CLI Example:
# Get detailed info on multiple processes
.\portmaster-cli.ps1 process-info 51008 # Individual analysis
.\portmaster-cli.ps1 process-info 30200 # Individual analysisWhat Multiple Process Analysis Shows:
Individual Details: Complete process info for each PID
Parent/Child Relationships: Process tree visualization
Network Analysis: Listening ports + active connections per process
Resource Summary: Combined memory usage and process type grouping
Process Chain: How processes relate to each other
Service Associations: Which processes belong to services
Example Output Summary:
Found: 2 of 2 processes
Total Memory: 113.7 MB
Process Types:
node: 2 instancesπ§ Advanced Configuration
PowerShell Execution Policy
If you encounter execution policy errors:
Set-ExecutionPolicy -ExecutionPolicy RemoteSigned -Scope CurrentUserCustom Port Ranges
The CLI supports flexible port specifications:
# Single ports
.\portmaster-cli.ps1 check-ports 80
# Multiple ports
.\portmaster-cli.ps1 check-ports 80,443,8080
# Port ranges
.\portmaster-cli.ps1 check-ports 3000-3010
# Mixed notation
.\portmaster-cli.ps1 check-ports 80,443,3000-3005,8080Environment Variables
Set these for customized behavior:
PORTMASTER_TIMEOUT- Command timeout in seconds (default: 30)PORTMASTER_FORCE_COLOR- Force colored output (true/false)
π€ Contributing
PortMaster MCP is designed with these principles:
π‘οΈ Security First - UAC elevation only when needed
π§ Extensible - Easy to add new commands and features
π― User-Friendly - Clear confirmations and error messages
π Comprehensive - Complete process and service lifecycle management
Development Setup
git clone <repository-url>
cd portmaster_mcp
pip install -r requirements.txt
# Test CLI
.\portmaster-cli.ps1 help
# Test MCP server
python portmaster_mcp.pyπ License
This project is provided as-is under the MIT License for managing Windows processes and services.
π Acknowledgments
Built for Claude Code MCP integration
Powered by Windows PowerShell and Python
Designed for Windows system administrators and developers
This server cannot be installed
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.