advisor-mcp
Related Servers
Alternatives to advisor-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that gives any AI coding tool a structured second opinion from another AI provider.10 npmMIT
- 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
- AlicenseAqualityBmaintenanceEnables coding agents and IDEs to request multi-model code review, architectural planning, and technical consultation over stdio, returning actionable diffs and SARIF diagnostics.3MIT
- AlicenseNot gradedqualityBmaintenanceEnables any MCP client to request an independent second opinion from a fresh Claude Code session without blocking, useful for plans, architecture, debugging, security reviews, and final checks.8 npmMIT
- AlicenseAqualityBmaintenanceEnables coding agents to request guarded code and architecture reasoning from multiple AI models through a single MCP server, with modes for direct answers, parallel councils, ordered chains, and structured debates, plus reusable context and audit tracing.28MIT
- AlicenseNot gradedqualityBmaintenanceMCP servers that let Claude Code delegate to other coding CLIs (Copilot, Codex, Gemini) for cross-model second opinions, structured reviews, and multi-engine consultations.MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct role: read state (get), write state (update), clear state (reset), invoke the model (consult), and check configuration (health). The get-vs-consult distinction is well clarified by descriptions, so an agent can reliably pick the right tool.
Four tools follow a verb_noun pattern (get/update/reset_advisor_session, consult_advisor), but advisor_health breaks it with a noun-only, verbless form. The deviation is minor and still readable.
Five tools is well-scoped for a session-backed advisor: one core consult plus a minimal state lifecycle and a health check. Every tool earns its place with no redundancy.
The session lifecycle is covered (get, update, reset, consult, health), with creation implied on first write. Only minor gaps exist, such as no list/enumerate operation for existing sessions.