mcp-server-manager

The project is designed for local MCP server management, explicitly stating that it supports only local servers and does not expose HTTP endpoints externally. Communication primarily occurs via standard I/O (stdio). It extensively uses `subprocess` and `os.system` for environment setup (pip, uv, creating scripts, opening terminals), which is common for such tools, but requires careful handling of user inputs to prevent command injection. User input for server names is sanitized. `psutil` is used for robust process management. No hardcoded secrets or obvious malicious patterns were found. The primary security risks are generally self-imposed by the user granting system-level permissions for local environment setup.