mirafleet
OfficialRelated Servers
Alternatives to mirafleet
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceA local MCP server that connects Claude Code to your work environment through auditable tools for file operations, API calls, and command execution, with safety gates and configuration.-
- AlicenseBqualityBmaintenanceSelf-hosted MCP server that lets Claude, ChatGPT and other AI assistants operate a Linux server safely: read-only by default, every change previewed and confirmed, secrets masked, full local audit log.18AGPL 3.0
- AlicenseAqualityDmaintenanceMCP server that wraps Docker, Caddy, and GitHub Actions operations on a remote VPS, enabling Claude to take read-then-write-with-confirmation infrastructure actions over SSH with a service allowlist and audit-trail-friendly responses.8MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that turns coding workflows into explicit execution graphs (DAG) with deterministic command execution, human-in-the-loop gates, and tamper-proof run history for Claude Code.3 npmMIT
- AlicenseAqualityDmaintenanceMCP server that lets any agent or MCP host delegate tasks to Claude Code running headless, with tools for review, validation, analysis, and autonomous work.42MIT
- AlicenseAqualityDmaintenanceA local MCP server that lets Claude Code orchestrate Codex CLI and OpenCode CLI as sub-agents with strict security, concurrency, and output limits.41MIT
TDQS
Scored across 24 tools
The set has several overlapping pairs: bash/exec, read/read_file, write/write_file, and bash_output/read_output. Descriptions clarify the remote-machine versus workspace distinction, but the naming does not, so an agent can still misselect among similar tools.
All names use lower snake_case, but conventions are mixed: single verbs like bash, exec, write, read, and grep coexist with verb_noun names like list_fleets, read_file, and workspace_open, plus noun_verb forms like job_list and bash_output. The pattern is readable but not predictable.
At 24 tools the set is heavy and sits at the top of the acceptable range. The domain is broad enough to justify many tools, but several overlapping execution and file tools could be consolidated.
The surface covers command execution, file reading/writing/editing, search/listing, transfers, background jobs, notebooks, workspaces, fleets, runners, and actions. Minor gaps such as explicit file deletion or move exist, but shell access provides workarounds.