SkillFoxx

Kimi Bridge for Claude Code MCP

kimi-bridge

An MCP server that turns a local Kimi Code CLI into a second agent inside Claude Code, with a dedicated BSL review tool for 1C

  • 0 ★ on the repository
  • Last commit
  • MIT
MCP server

Broad access

Why this level

  • Spawns Kimi Code CLI as a second agent that runs its own tools
  • Per the README Kimi runs without a sandbox and can write files in its working directory
All reasons and checks
Russian stack

byyshka/kimi-bridgeAuthor:byyshka

Install

Manual install

npm i -g @moonshot-ai/kimi-code@0.31.1

Installs the exact Kimi Code CLI version the bridge's output parsing is written for. Run kimi login afterward.

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Spawns Kimi Code CLI as a second agent that runs its own tools
  • Per the README Kimi runs without a sandbox and can write files in its working directory

This is third-party code. Review the repository files before installing.

What it does

The server spawns a locally installed Kimi Code CLI and exposes it to Claude Code as a second agent: it starts the process, parses its streamed output, manages sessions and timeouts, and summarizes which tools were actually called. A dedicated kimi_review tool, registered only in the default profile, casts Kimi as a BSL code reviewer that checks metadata through its own graph MCP servers instead of guessing. The neutral profile exposes only the general kimi_ask tool with no 1C specifics.

Who it is for. For 1C developers on Claude Code who want Kimi as a second agent for BSL code review against real metadata.

Good fit when

  • You want a second agent inside Claude Code for parallel work
  • You need a BSL reviewer that checks attributes against real metadata via MCP instead of recalling them
  • You already have Kimi Code CLI installed and authorized

Not a fit when

  • You do not work with 1C:Enterprise: you get a plain bridge with no review tool
  • Kimi Code CLI 0.31.1 is not installed and logged in
  • You are not on Windows: the POSIX branches in the code are untested

Example request

Ask Kimi to review this BSL module and verify the attributes against the configuration metadata

MCP

Transport
stdio
Authentication
not required

Environment variables

KIMI_BRIDGE_ENTRY
Explicit path to dist/main.mjs when Kimi CLI is installed outside the default npm package.

Limitations

The bridge installs and authenticates nothing by itself: it needs a separately installed and logged-in Kimi Code CLI 0.31.1, installed via npm rather than the one-line installer. The version is pinned hard because the stream parsing is written against it; @latest currently resolves to the untested 2.x line. Built and tested on Windows 11 only.

How to disable. Remove the kimi-bridge server from Claude Code MCP settings and, if it is no longer needed, uninstall Kimi Code CLI separately.

FAQ

Why is the Kimi CLI version pinned?

The bridge's stream parsing is written and tested against 0.31.1; the newer 2.x line is untested.

Does BSL review work outside 1C projects?

The kimi_review tool is registered only in the default profile. The neutral profile exposes only the general kimi_ask tool with no 1C specifics.

Discussion

No questions or reviews yet.

All 1C:Enterprise tools
Russian stack

MCP bridge to BSL Language Server: navigation, diagnostics and refactoring of 1C and OneScript code for agents

MCP serverExtended access71

BSL Language Server for Claude Code

BSL Language Server Claude Code Plugin

Russian stack

A Claude Code plugin that attaches BSL Language Server to 1C and OneScript files: diagnostics, go to definition, references, formatting

PluginExtended access37
Russian stack

An MCP server that exposes the cloud 1C:Napparnik (1C.ai) assistant and a local BSL Language Server to agents in Cursor and other IDEs

MCP serverExtended access22
Russian stack

An MCP server plus a 1C external data processor that lets an agent run queries and code in the user's already open session, with no gateway in between

MCP serverBroad access13
Russian stack

A stdio proxy between Claude Code and the client_mcp server inside 1C that reconnects itself after 1C restarts without a manual /mcp

MCP serverExtended access

README in short

The README carefully explains the bridge is a thin adapter that installs and authenticates nothing on its own. It covers the required npm install with a pinned version, OAuth or API key login, the purpose of kimi_review for BSL review, and the difference between the default and neutral profiles. It also documents the KIMI_BRIDGE_ENTRY variable for a nonstandard dist/main.mjs path.

README badge

Report a problem