Skip to main content
Glama
briandconnelly

moonbridge

by briandconnelly
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to moonbridge

No user-submitted related servers found.

    Related Servers

    • kimi-acp-mcp

      TuTouPower
      A
      license
      A
      quality
      B
      maintenance
      Bridges Claude Code to Kimi Code via MCP, enabling task delegation with file and command execution.
      3
      MIT

    • Kimi MCP Server

      MichaelCecil
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP bridge that enables Claude Code to consult the Kimi AI model in a structured challenge-loop for code review, debugging, and architecture evaluation.
      17 npm
      2
      MIT

    • Kimi MCP Server

      x51xxx
      A
      license
      A
      quality
      D
      maintenance
      Bridges MCP clients to Moonshot AI's Kimi Code CLI, enabling file analysis, brainstorming, batch tasks, code reviews, and session management within editors like Claude Desktop and Cursor.
      14
      522 npm
      1
      MIT

    • claude-ask

      AbsoluteMode
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables users to request a second opinion from a locally authenticated Claude Code model via MCP tools, supporting asynchronous jobs with restricted tools for safety.
      MIT

    • kimi-bridge

      byyshka
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to delegate questions and BSL code reviews to a locally installed Kimi Code CLI, running it as a second agent with its own MCP servers and optional neutral profile.
      MIT

    • Kimi Code MCP

      lxq020801
      A
      license
      B
      quality
      C
      maintenance
      Bridges Codex Desktop with Kimi Code CLI, enabling direct control of AI coding sessions via MCP tools for prompt, status, cancel, and CLI operations.
      1
      18 npm
      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

    A4.4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: setup introspection, model/capability discovery, three separate paid operation modes, their async counterparts, per-mode dry runs, and job lifecycle management. Even the job tools split cleanly into status, result, consume, cancel, and list functions.

    Naming Consistency5/5

    All tools share the kimi_ prefix and snake_case convention, with predictable suffixes like _async, _dry_run, and kimi_job_*. The naming is uniform and easy to navigate even though discovery tools are noun-style while operation tools are verb-style.

    Tool Count4/5

    At 16 tools, this is slightly above the typical well-scoped range, but the count is justified by the three natural groups: metadata/status, paid operations with dry-run and async variants, and job lifecycle. No tool feels redundant, though the surface is a bit large.

    Completeness5/5

    The tool surface covers the full intended workflow: preflight status, capability and model discovery, three operation modes, dry-run previews, and a complete async job lifecycle from start through list, status, fetch, consume, and cancel. Sync calls also expose job IDs for recovery, leaving no obvious dead ends.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources