Commander Plus
Related Servers
Alternatives to Commander Plus
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA portable AI control plane that lets connected MCP hosts, chat clients, and messaging channels share persistent memory, versioned skills, unified search, permission-gated tools, sandboxed code execution, browser automation, and queued tasks.MIT
- AlicenseNot gradedqualityBmaintenanceProvides a local-first AI workspace for chatting, invoking skills, managing projects, and integrating MCP tools, with all data stored on the user's machine.2Apache 2.0
- AlicenseBqualityBmaintenanceSovereign, deterministic, local-first context and DAG lifecycle engine with native stdio MCP server for autonomous AI coding agents.23MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for task management, project knowledge, workspace trust, runner sandboxes, extension registry, and workflow prompts, enabling AI agents to manage tasks and collaborate locally.5,117 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceA local-first mission control for AI agent harnesses, providing a unified MCP gateway for shared memory, task queue, and encrypted secrets across multiple agents.2MIT
- AlicenseAqualityCmaintenanceMCP server that enables running and managing file-based AI Skills, Agents, and Flow workflows as DAGs, with tools for listing, executing, and resuming tasks via stdio JSON-RPC.9MIT
TDQS
Scored across 5 tools
Workspace register vs list are clearly paired but distinct, and skill_save vs skill_route are clearly separated by action. The only slight ambiguity is between workspace_list and guardian_workspace_health, which both report on registered workspaces from different angles (enumeration vs readability).
All names are snake_case verb_noun style (workspace_register, skill_save, skill_route) which is predictable. The outlier is guardian_workspace_health, which uses a subsystem prefix rather than a verb, breaking the pattern for that one tool.
Five tools is a compact, well-scoped set for workspace registration plus local skill routing, with no filler. It sits slightly on the thin side, particularly on the skill side where a single save/route pair carries the whole capability.
There is save and route for skills but no skill list, update, or delete, and workspace_register has no corresponding unregister/remove counterpart. The surface covers the happy path but leaves obvious lifecycle gaps an agent would hit when managing or cleaning up entries.