mcp-node-zig
Related Servers
Alternatives to mcp-node-zig
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceAn all-in-one self-hosted remote MCP server and gateway that lets AI clients access filesystem, terminal, background processes, and computer-use tools, and multiplex local stdio MCP servers over Streamable HTTP on Linux, Jetson, macOS, and Windows. It bundles revocable API keys, OAuth 2.0, and a read-only/coding safety switch so cloud and desktop assistants can safely drive remote machines.151,127 npm1MIT
- AlicenseNot gradedqualityBmaintenanceTurns any Linux server into an AI-agent-accessible machine over HTTPS, allowing MCP clients like ChatGPT, Claude, and Grok to securely control files, run shell commands, inspect system state, query SQLite, and work with git behind a bearer token.76 npm4MIT
- FlicenseNot gradedqualityNot gradedmaintenanceA secure and pluggable MCP server to run terminal commands on your local machine or cloud server — remotely, safely, and with LLMs or agentic clients.-
- AlicenseAqualityCmaintenanceMCP server for SSH and local terminal access. Supports interactive commands, long-running processes, and TUI apps like tmux/zellij64MIT
- AlicenseNot gradedqualityBmaintenanceA remote Streamable HTTP MCP server that lets web clients like Claude.ai and ChatGPT manage cloud machines with OAuth login — creating, starting, pausing and deleting machines, running commands, reading and writing files, managing snapshots and public ports, and driving an optional Linux desktop via screenshots and input actions. Long-running work can be backgrounded and operations polled, so browser-based clients stay within their timeouts.MIT
- FlicenseAqualityBmaintenanceCross-platform MCP server for policy-controlled command execution on Linux and Windows, with no SSH dependency.3-
TDQS
Scored across 13 tools
The nine exec_* tools form a coherent session lifecycle (start/poll/wait/write/kill/close/list) with distinct roles, and the file tools (read_file/write_file/list_dir) are clearly separate. The main overlap is the trio exec vs exec_shell vs exec_start and the fact that exec_poll and exec_wait return identical payloads, which could cause occasional misselection.
All names are lowercase snake_case following a predictable verb_noun pattern. The exec_* family is systematically prefixed, and file tools (read_file/write_file/list_dir) and sys_info-adjacent tools follow consistent conventions throughout.
13 tools is well within the ideal range and each tool earns its place. The session lifecycle is broken into focused operations rather than being crammed into one overloaded tool, and the file/host operations round out the set without bloat.
The surface covers process execution (one-shot, shell, and session-based), full file read/write/list, and host info, which is solid lifecycle coverage. Minor gaps remain (no file delete/stat/move/copy), but these are workaroundable via exec/exec_shell.