BoteX
Related Servers
Alternatives to BoteX
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.333 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables 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 gradedqualityBmaintenanceEnables 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 gradedqualityBmaintenanceEnables MCP clients like Codex and DSH to invoke DeepSeek subagents for inspect, plan, review, and implement tasks, with write protection, rollback, and status reporting.6 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
- AlicenseNot gradedqualityAmaintenanceEnables any MCP-compatible client to run reusable, Markdown-defined coding agents (such as code reviewers, test writers, or investigators) through a chosen coding CLI backend. Supports shared backend and model configuration across clients, permission levels, and session continuation for longer tasks.294 npmMIT
TDQS
Scored across 12 tools
Most tools target clearly distinct resources or actions, but start_task and run_subagent both execute BoteX tasks with nearly identical arguments, so agents may hesitate over sync vs detached execution. The descriptions explicitly explain the async contract and task_id polling, so the overlap is recoverable rather than fatal.
All tools use snake_case with a predictable verb_noun or verb pattern (start_task, get_stats, check_health, save_memory). There are no mixed conventions or vague names, making the set easy to scan and remember.
At 12 tools, the server is well scoped for its apparent domain: task execution, task status/stats, diagnostics, model recommendation, URL fetch, outline extraction, and memory vault operations. Each tool appears to earn its place rather than padding the surface.
Core task execution is covered with run_subagent/start_task and get_task_status, but there is no cancel_task or list_tasks, which can strand detached tasks. The memory vault supports save/search/read but lacks delete/update/list-all, creating notable lifecycle gaps even if some workarounds exist.