fauxnix
Related Servers
Alternatives to fauxnix
- AlicenseNot gradedqualityBmaintenanceProvides a local Windows control plane for PowerShell and AI CLIs, exposing MCP tools for safe terminal sessions, bounded provider calls, routing, committees, and run receipts.5 npmMIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceRemote-first, model-independent Windows execution MCP for ChatGPT, Claude, Gemini, and other MCP-compatible AI clients.MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI clients to securely control and interact with a local Windows machine through 218 configurable tools for files, Git, processes, Windows UI, browser automation, WSL, Office, recovery, skills, and child MCP servers.11 npmMIT
- AlicenseNot gradedqualityAmaintenanceA native Windows terminal multiplexer with MCP bridge for AI agents, enabling browser automation, multi-agent coordination, and terminal control.398MIT
- AlicenseBqualityDmaintenanceHigh-performance MCP server giving AI agents advanced filesystem and automation capabilities on Windows, with 26 tools across file I/O, search, Git, process management, and more.262MIT
- AlicenseAqualityAmaintenanceA Windows-native MCP gateway that lets any MCP-capable host orchestrate local coding-agent CLIs as external workers.11Apache 2.0
- FlicenseNot gradedqualityAmaintenanceEnables AI assistants to execute PowerShell commands, manage files, inspect projects, run Git operations, and monitor system information on Windows through a local MCP server.-
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose: bash executes a single command, bash_batch runs a preplanned multi-step workflow, fauxnix_translate shows the PowerShell translation, and fauxnix_session inspects/resets session state. The one potential overlap between bash and bash_batch is explicitly resolved by their descriptions.
The names are all lowercase and grouped by prefix (bash vs fauxnix), but they do not follow a consistent verb_noun convention. One bare noun tool, one noun_noun tool, and one noun_verb tool makes the pattern only partially predictable.
Four tools is well-scoped for this server's purpose: single execution, batch execution, translation/debugging, and session management. Each tool earns its place without redundancy.
The tool surface fully covers the stated domain: execute commands, run batches, translate for debugging, and manage session state. There are no obvious gaps for a bash-compatibility focused server.