embedded-mcp-toolkit
Related Servers
Alternatives to embedded-mcp-toolkit
No user-submitted related servers found.
Related Servers
- GPL 3.0
- AlicenseNot gradedqualityCmaintenance一个基于 MCP 协议的 Electron 桌面终端应用,为 AI 助手提供安全的远程 shell 执行能力。8 npm24MIT
- AlicenseAqualityCmaintenanceA secure remote server management tool based on MCP protocol, supporting SSH connections, command execution, and SFTP file transfers.207 npm6MIT
- AlicenseAqualityDmaintenanceWindows-focused MCP server for terminal automation with persistent PowerShell sessions, live session logs, and VS Code integrated terminal bridge.6MIT
- AlicenseNot gradedqualityCmaintenanceA lightweight, zero-agent SSH operations tool that enables remote command execution, file transfer, and audit logging. It integrates as an MCP server for AI-driven infrastructure management.5 npmMIT
- AlicenseBqualityAmaintenanceMCP server enabling local network interaction, shell command execution, system resource monitoring, and SSH-based remote device management.18MIT
TDQS
Scored across 38 tools
Tool purposes are mostly clear due to transport prefixes and distinct verbs, but a few pairs blur boundaries: ssh_shell_open vs ssh_shell_login/serial_shell_login are convenience wrappers around open, and adb_exec vs adb_shell_exec differ only in whether a persistent session is used. The detailed descriptions help resolve these, so the overlap is manageable but not zero.
The core convention is [transport]_[action] (e.g. ssh_shell_exec, serial_exec, adb_shell_open), but it is applied unevenly: serial_open/serial_close lack the 'shell' segment used by ssh_shell_open/adb_shell_open, adb_exec sits alongside adb_shell_exec with a different implication, and several tools use a _tool suffix (version_tool, port_scan_tool, greet_tool) while others do not. Still readable, but the conventions are mixed.
At 38 tools, this exceeds the 25+ heavy threshold. The count is inflated by triplicating nearly identical session operations across SSH, serial, and ADB, plus a set of one-off utility tools; while systematic, it creates real selection overhead for agents.
The toolkit provides comprehensive lifecycle coverage for SSH, serial, and ADB sessions (open/read/write/exec/close), file transfer in both directions, U-Boot control, and environment metadata. Minor gaps exist—ADB file transfer is only available via generic adb_exec, and there is no dedicated reboot/port-forwarding tool—but these are workable without dead ends.