PC-Fixer MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pc_fixer_diagnoseC | Run deep multi-tier diagnostics across workspace code, operating system environment, virtual environments, Git repository locks, PEP 517 build configs, AST syntax, and CWE vulnerabilities. |
| pc_fixer_auto_healA | Autonomously heal detected codebase and environment defects with automatic backup and atomic rollback manifest. Safe with dry-run verification mode. |
| pc_fixer_rollbackA | Roll back a previously executed healing transaction using its unique transaction ID, restoring modified files to their exact pre-fix state. |
| pc_fixer_check_systemC | Check physical hardware health, disk partitions space, WSL2 vhdx growth, high-memory consumer processes, and active developer port conflicts (3000, 5000, 8000, etc.). |
| pc_fixer_cwe_auditB | Execute local AST static security vulnerability scan against OWASP Top 10 and CWE catalog (CWE-78 Command Injection, CWE-89 SQL Injection, CWE-22 Path Traversal, CWE-798 Hardcoded Secrets). |
| pc_fixer_kill_port_processB | Find and terminate the process locking a specific developer port (e.g. 3000, 5000, 8000, 8080) to unblock dev servers without rebooting. |
| pc_fixer_clean_git_locksA | Find and remove stale Git lock files (.git/index.lock, .git/HEAD.lock, refs locks) that block git operations after crashes or aborted commands. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
Most tools are distinct, but pc_fixer_diagnose explicitly claims to cover 'Git repository locks' and 'CWE vulnerabilities,' directly overlapping with the dedicated pc_fixer_cwe_audit and pc_fixer_clean_git_locks tools. An agent wanting a security scan or git-lock cleanup could reasonably misselect between the broad diagnose tool and the specialized ones, though descriptions do help differentiate.
All tools share a consistent pc_fixer_ prefix and snake_case convention, which is a strong unifying pattern. However, action ordering is mixed (check_system and kill_port_process are verb_noun, while cwe_audit is noun_verb and rollback/diagnose are bare verbs), a minor deviation from a uniform verb_noun scheme.
Seven tools is well within the ideal 3-15 range for a PC/codebase fixing server. Each tool maps to a distinct concern (diagnose, heal, rollback, system health, security audit, port kill, git locks) and earns its place without bloat.
The lifecycle of diagnose -> heal -> rollback is covered, along with system checks and targeted fixes, giving strong overall coverage. The one gap is discoverability of transaction IDs: pc_fixer_rollback requires a transaction ID but there is no tool to list prior healing transactions, forcing reliance on manifests returned by heal.