shield_lock
JinDaGe
Contact
← Back to MCP directory
publicPublicdnsLocal runtime

kibitz

Kibitz 是一个专为专业人士设计的编码助手，旨在提升开发效率。它通过提供一个本地开发服务器，允许用户在浏览器中直接进行编码操作。Kibitz 支持通过 Anthropic API 进行高级配置，并允许用户自定义系统提示和模型设置。此外，Kibitz 还支持与 MCP 服务器的集成，用户可以通过配置 MCP 服务器来扩展其功能。Kibitz 的配置是按项目进行的，创建新项目时会继承部分配置，如 API 密钥和模型设置，但不会复制 MCP 服务器配置。Kibitz 还支持为 Kinode 构建，通过指定基础路径和默认 WS-MCP 服务器 URI 来定制化部署。

article

README

kibitz

The coding agent for professionals

https://github.com/user-attachments/assets/3f8df448-1c81-4ff2-8598-c48283a4dc00

Prerequisites

  • git
  • npm

Installation

  1. Clone the repository:
git clone https://github.com/nick1udwig/kibitz.git
cd kibitz
  1. Install dependencies:
npm install
  1. Run the development server:
npm run dev
  1. Open http://localhost:3000 in your browser.

Configuration

  1. Open the Settings panel in the UI
  2. Enter your Anthropic API key (Get one here).
  3. Optionally set a system prompt
  4. Configure MCPs by running them using ws-mcp and then connecting to them in the Settings page

Note configuration is PER-PROJECT. When creating a new project, it will use some, but not all, of the current project's configuration: the API key, model, and system prompt will be copied over, but MCP servers will not.

Building for Kinode

  1. Add a base to the endpoint by building with the NEXT_PUBLIC_BASE_PATH (MUST start with a /),
  2. Change the default WS-MCP server URI by specifying NEXT_PUBLIC_DEFAULT_WS_URI (MUST start with a /),

like so:

NEXT_PUBLIC_BASE_PATH=/kibitz:kibitz:nick.kino NEXT_PUBLIC_DEFAULT_WS_URI=/fwd-ws:kibitz:nick.kino npm run build

and then copy the contents of out/ into the package's pkg/ui/ dir.

help

Runtime guide

cloud

Hosted runtime

Hosted servers run from a provider-managed environment. You usually connect the MCP client to the hosted endpoint or follow the provider's authorization flow, without keeping a local process alive

  1. Open provider connection page
  2. Authorize or copy endpoint
  3. Connect from your MCP client
terminal

Local runtime / other methods

Local servers run on your own machine or infrastructure. You normally copy the server_config into your MCP client, install the required package, and provide env variables from env_schema when needed

  1. Copy server_config
  2. Install required package
  3. Fill env variables and restart client