severally
Related Servers
Alternatives to severally
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceEnables AI agents to consult expert models (Claude, GPT, Gemini, DeepSeek, Z.ai) for technical guidance, code reviews, and architectural advice without switching context.435 npm4MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to request a second opinion from a different frontier model via a single tool call, with PII scrubbed before transit, live web search, and support for Claude, ChatGPT, Cursor, and Gemini.Apache 2.0
- AlicenseAqualityBmaintenanceGet a second opinion on your code from every coding agent you have. Claude Code, Codex and Grok review each other's diffs and answer each other's questions, even inside a session that's already running. Uses the CLIs you're signed in to, no API keys.4207 npm1MIT
- AlicenseAqualityBmaintenanceEnables one AI coding agent to delegate tasks to, and build consensus across, multiple other coding CLIs (Claude Code, Codex, etc.) by orchestrating them as headless subprocesses.1949 PyPI7MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI coding agents to consult a multi-model deliberation council before irreversible, high-stakes decisions, returning structured architectural decision records with consensus and dissenting risks.1-
- AlicenseNot gradedqualityDmaintenanceEnables multiple AI agents to share and read each other's responses to the same prompt, allowing them to reflect on what other LLMs said to the same question.2MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct action in the consultation lifecycle: start, cancel, wait/get, list, export, and record checks. The read-oriented tools are separable by scope: consult_get waits for live results, consult_list summarizes recent runs, and consult_export renders a full Markdown artifact.
All names follow the same consult_<verb> snake_case pattern with clear verbs. There is no mixing of camelCase, vague verbs, or inconsistent prefixes.
Six tools is a well-scoped surface for consultation orchestration. Each tool earns its place by covering a distinct lifecycle operation without obvious redundancy.
The set covers starting, cancelling, waiting on, listing, exporting, and recording checks for consultations. Minor gaps remain around explicit consultant/target discovery and history cleanup or deletion, but these are mostly workable through consult_start and existing filters.