BoteX
Related Servers
Alternatives to BoteX
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to delegate work to nested subagents running on Codex and Claude Code, keeping each task's session, turn history and results durable in SQLite while the main chat continues. Supports async or blocking waits, mid-session context updates, git worktree isolation, read-only-by-default permission inheritance, and cancelling whole subagent trees.MIT
- AlicenseNot gradedqualityCmaintenanceEnables delegating tasks to agents you configure yourself through OpenAI-compatible Chat Completions backends, with automatic or explicit routing, synchronous calls, persistent asynchronous jobs, and multi-step reviewed workflows. It returns proposals and analyses only, leaving file changes, command execution, and approvals under the MCP client's control.18 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP-capable coding assistants to delegate repository investigation, bounded implementation work, and noisy command runs (tests, builds, linters) to sandboxed OpenCode agents. Each role can use an independently selected model, and only concise results are returned to the parent agent, which keeps responsibility for architecture and high-risk operations.MIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to route coding tasks across local and cloud models with explicit budgets, repository planning and execution, and independent validation/repair checks.Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients like Codex and DSH to invoke DeepSeek subagents for inspect, plan, review, and implement tasks, with write protection, rollback, and status reporting.1,160 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables MCP-capable coding agents to perform batched, token-efficient file and search operations with tolerant, automatically verified edits and diffs. It supports sandboxed workspace access, optional command execution, caching, and post-edit syntax/import checks.MIT
TDQS
Scored across 18 tools
Most tools have clearly distinct targets: memory CRUD (save/search/read/delete/patch), graph tools (get_backlinks, find_graph_health), admin (check_health, clean_snapshots, get_stats), and file/web access (get_outline, fetch_url). The main friction point is run_subagent vs start_task, which expose nearly identical argument surfaces and differ only in sync vs detached execution — well documented, but an easy misselection. search_memory vs read_memory vs read_scratchpad are separable but require reading descriptions to distinguish.
Every tool follows a consistent snake_case verb_noun pattern (fetch_url, get_task_status, save_memory, patch_memory_section, init_obsidian_vault). Verbs are used predictably (get_* for retrieval, *_memory for vault ops, run_/start_ for engine invocation). No camelCase or stylistic outliers.
18 tools is on the heavier side but each maps to a real capability across three sub-domains (engine execution, memory vault, environment/admin). Nothing looks like filler, though the admin trio (check_health, clean_snapshots, get_stats) plus Obsidian init could plausibly be consolidated. Slightly over-scoped rather than bloated.
Memory vault coverage is strong (create/read/search/patch/delete/backlinks/graph-health/Obsidian export) and the task lifecycle covers start, poll, and synchronous run. The notable gap is the absence of a cancel_task tool even though CANCELLED is an advertised status, and there is no explicit list_memories or full-content update (only section patching) — agents can mostly work around these via search_memory and max_duration_s.