Skip to main content
Glama
Chao-Shiun

claude-consult-mcp

by Chao-Shiun
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to claude-consult-mcp

No user-submitted related servers found.

    Related Servers

    • Claude MCP for Codex

      daron4ever
      A
      license
      A
      quality
      B
      maintenance
      Enables Codex to consult Claude Code for a second opinion through a local stdio MCP server, exposing the ask_claude tool for text-only reviews and recommendations using existing Claude Code authentication. Codex can request findings and tradeoff analysis without allowing Claude to edit files or run commands.
      1
      1
      MIT

    • Clonst

      capritora
      A
      license
      A
      quality
      B
      maintenance
      Enables adversarial code review by connecting Claude Code to OpenAI Codex, iterating until consensus is reached between the two AI models.
      3
      18 npm
      1
      MIT

    • codex-subagent-mcp

      parisbs
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude Code to delegate coding tasks—investigation, review, long-running background jobs, and optional file edits—to a locally installed OpenAI Codex CLI, with the model and reasoning effort chosen per task and read-only execution by default. Follow-up requests reuse Codex's existing context, and write-enabled delegations can be confined to a managed git worktree so the user's own checkout stays untouched.
      9
      156 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.6/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct interaction mode with Claude: general questions, continuing conversations, structured debates, multi-perspective panels, diff and file reviews, adversarial opinions, and session management. Overlap is minimal and clearly delineated by descriptions.

    Naming Consistency5/5

    All tools follow a consistent 'claude_verb_noun' pattern in snake_case (e.g., ask_claude, claude_debate_open, claude_review_files). No mix of styles or ambiguous verbs.

    Tool Count5/5

    With 9 tools covering diverse consultation workflows (Q&A, debates, reviews, session management), the count is well-scoped for a consultant MCP. Each tool serves a clear purpose without redundancy.

    Completeness5/5

    The tool surface covers the full lifecycle of Claude interaction: starting conversations, continuing them, debating, requesting panel reviews, reviewing code changes or files, getting adversarial critiques, and managing sessions. No obvious gaps for the stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources