Windows task management MCP server for process listing, killing, and port monitoring
Server has 5 tools with clear verb-noun naming (list_, kill_, get_, find_) and proper tool annotations (readOnlyHint). Descriptions are present and adequate (60-120 chars each). Input schemas are visible with typed parameters. However, output schemas are not documented, responses are text-only without structured field definitions. Parameter descriptions lack detail on constraints, ranges, and error cases. No pagination support for list_processes despite potentially large result sets. Error handling is minimal, no guidance on recovery or actionable next steps.
Find which process is using a TCP or UDP port (IPv4 and IPv6). Returns PID, process name, protocol, and connection state.
Get details for one process: name, parent PID, threads, memory usage, executable path, and command line. Use the command line to tell apart multiple processes with the same name (e.g. several node.exe).
Kill a Windows process by PID. Set tree=true to also kill all child processes (the whole process tree).
Kill the process that is using a TCP or UDP port (IPv4 and IPv6). Single-step: finds the process and kills it. Set tree=true to also kill its child processes.
List running Windows processes (pid, name, parent pid). Optionally filter by name.
Output schemas not documented. All tools return TextContent with unstructured text. LLMs cannot parse fields or plan downstream calls. Responses should be structured JSON with typed fields (pid, name, memory_mb, etc.).
Parameter descriptions lack constraints and ranges. 'port' parameter has no range (valid 1-65535?). 'pid' has no validation guidance. Descriptions should state: 'TCP/UDP port number (1-65535)' and 'Process ID (positive integer)'.
No pagination for list_processes. If hundreds of processes run, response could be massive. Should accept limit and offset parameters, return total count, and cap results at 50 by default.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 57 | 2026-07-28+ | v2 |
Error handling lacks recovery guidance. No indication of what to do if process not found, port invalid, or kill fails. Errors should be actionable: 'Process 12345 not found. Call list_processes to find valid PIDs.'
Destructive tools (kill_process, kill_process_by_port) lack confirmation or dry-run support. Agents can accidentally kill critical processes. Should support a 'dry_run' parameter or require explicit confirmation.