Skip to main content
Glama
HoziMurayama

MCP Rubber Duck

Official
by HoziMurayama
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to MCP Rubber Duck

No user-submitted related servers found.

    Related Servers

    • agent-rack

      lakpriya1s
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that bridges CLI coding agents like Claude Code, Codex, opencode, and Antigravity into any MCP client, enabling synchronous and asynchronous task execution, follow-up input, and a structured code review tool.
      94 npm
      1
      MIT

    • mcp-rubber-duck

      nesquikm
      A
      license
      A
      quality
      A
      maintenance
      An MCP server that acts as a bridge to query multiple OpenAI-compatible LLMs with MCP tool access. Just like rubber duck debugging, explain your problems to various AI "ducks" who can actually research and get different perspectives!
      12
      773 npm
      176
      MIT

    • personal-mcp

      buYoung
      F
      license
      Not graded
      quality
      A
      maintenance
      MCP server that bridges coding agents (Claude Code, Codex, Gemini CLI) via ACP for pair programming, enabling agents to consult each other as tools.
      3
      -

    • MCP Coding Agents

      kadreio
      A
      license
      Not graded
      quality
      D
      maintenance
      A transport-agnostic MCP server that integrates multiple AI coding agents (Claude Code, Gemini, and Codex) with built-in tools for command execution, calculations, and streaming capabilities. Supports both STDIO and HTTP transports for flexible deployment.
      2 npm
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 12 tools

    Disambiguation3/5

    Most tools have distinct purposes, but compare_ducks and duck_council both retrieve responses from multiple ducks, creating potential confusion. The other multi-duck tools (vote, judge, iterate, debate) are well-separated, but the overlap between these two is notable.

    Naming Consistency2/5

    Tool naming is inconsistent: list_ducks, list_models, ask_duck, chat_with_duck, clear_conversations, and get_usage_stats follow a verb_noun pattern, while duck_council, duck_vote, duck_judge, duck_iterate, and duck_debate use a 'duck_' prefix with the action as a suffix. compare_ducks also breaks the pattern by placing the verb first. This mixed style makes tool names less predictable.

    Tool Count5/5

    12 tools is a well-scoped count for this server's purpose of managing and interacting with multiple LLM providers. It covers basic listing, single queries, conversations, multi-duck collaboration modes, and usage tracking without feeling bloated.

    Completeness4/5

    The toolkit covers the core workflow well: listing providers and models, asking questions, maintaining conversations, running multi-duck scenarios, and tracking usage. A minor gap is the lack of a tool to fetch or manage individual conversation histories, but this is not critical for the primary use cases.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources