linux-mcp-server
Related Servers
Alternatives to linux-mcp-server
No user-submitted related servers found.
Related Servers
FlicenseBqualityDmaintenanceMCP server for managing Ubuntu servers with AI integration, enabling system monitoring, Docker control, Gitea repository management, Ollama LLM interaction, workspace file operations, and Claude Code assistant via natural language.34-- AlicenseAqualityBmaintenanceMCP server for managing multiple SSH servers via AI assistants, offering tools for remote command execution, file operations, and system monitoring.1153 PyPI2MIT
- AlicenseBqualityFmaintenanceAn MCP server that allows AI models to execute system commands on local machines or remote hosts via SSH, supporting persistent sessions and environment variables.118 npm28MIT
- AlicenseNot gradedqualityCmaintenanceAn MCP server for managing remote SSH servers, enabling AI agents to execute commands, transfer files, and perform deployment operations securely.MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for remote Linux server administration via SSH, integrating with Claude Code to manage Ubuntu/Debian servers.2-
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI assistants to manage SSH terminal sessions, execute commands, and automate server operations through natural language, with multi-tab support and session persistence.MIT
TDQS
Scored across 47 tools
Most tools target distinct resources, but there are overlapping pairs: zfs_get_property can read from pools while zfs_pool_get_property also does; list_processes and get_top_processes both return top processes; tail_file and search_logs/get_journal_logs overlap on logs. Descriptions mitigate some confusion but boundaries are not always crisp.
Naming is largely predictable with verb_noun or prefix_action patterns (apt_*, service_*, zfs_*). Minor inconsistencies exist like zfs_pool_status vs zfs_list_pools and zfs_pool_get_property vs zfs_get_property, but overall the set is readable and consistent.
47 tools is well above the 25-tool threshold for 'too many' despite covering many domains. The breadth may justify some tools, but the set feels heavy and could be consolidated (e.g., ZFS pool vs dataset property tools).
Covers system info, packages, services, files, commands, ZFS, logs, and processes—broad for Linux administration. Gaps like user management or network configuration can be handled via run_command, so core lifecycle is mostly complete.