qodercli-mcp

A minimal MCP server that wraps qodercli (Qoder CLI), letting any MCP client delegate coding tasks to a local Qoder agent.

一个极简的 MCP server，把本地的 qodercli（Qoder CLI）包装成 MCP 工具，让任意 MCP 客户端（Qoder IDE、Claude Code、Cursor 等）可以像调用子 Agent 一样调用 Qoder。

Why / 为什么

Some CLI agents ship an official MCP server mode (e.g. codex mcp-server), but qodercli currently only acts as an MCP client. This project fills that gap with a thin wrapper: it spawns qodercli -p <prompt> under the hood and streams the result back over MCP stdio.

部分 CLI Agent 自带官方 MCP server 模式（如 codex mcp-server），但 qodercli 目前只能作为 MCP 客户端。本项目用一个薄包装层补上这个缺口：内部调用 qodercli -p <prompt>，把结果通过 MCP stdio 返回。

Features / 功能

• ask-qoder tool — delegate a prompt to qodercli

• ask-qoder 工具 —— 把任务委托给 qodercli

• Structured output (session_id, is_error, duration_ms, total_credits, num_turns) via -o json parsing

• 结构化输出（session_id、is_error、duration_ms、total_credits、num_turns），自动解析 -o json

• list-sessions tool to discover resumable sessions

• list-sessions 工具，用于发现可续接的会话

• list-models tool for runtime model discovery (no stale model lists)

• list-models 工具，运行时发现可用模型（不依赖过时清单）

• reasoning_effort parameter (--reasoning-effort)

• reasoning_effort 参数（透传 --reasoning-effort）

• Server instructions in the MCP initialize result guide clients on usage

• MCP initialize 结果携带服务器使用说明，引导客户端正确调用

• Codex-style sandbox levels (read-only / workspace-write / danger-full-access)

• 仿 codex 的 sandbox 分级（read-only / workspace-write / danger-full-access）

• System prompt injection (system_prompt / append_system_prompt)

• 系统提示注入（system_prompt / append_system_prompt）

• Working directory, model, permission mode, output format control

• 支持指定工作目录、模型、权限模式、输出格式

• Session resume (resume_session_id) for multi-turn delegation

• 支持会话续接（resume_session_id），可多轮委托

• Timeout protection with SIGKILL fallback

• 超时保护（超时自动 SIGKILL）

• Proxy quota support (HTTP_PROXY / HTTPS_PROXY injection)

• 代理额度支持（HTTP_PROXY / HTTPS_PROXY 注入）

• Zero build step — plain ESM JavaScript, Node.js >= 18

• 无需构建 —— 纯 ESM JavaScript，Node.js >= 18

Prerequisites / 前置条件

1. Node.js >= 18

2. qodercli installed and signed in (qodercli login)

Install / 安装

Option A — npx (recommended / 推荐): no clone needed, the MCP client downloads the package on first use. 无需克隆，MCP 客户端首次使用时自动下载：

"command": "npx", "args": ["-y", "qodercli-mcp"]

Option B — from source (for development / 开发用):

git clone https://github.com/cantbeblank96/qodercli-mcp.git
cd qodercli-mcp
npm install

MCP client configuration / MCP 客户端配置

Qoder IDE

Add to ~/.qoder/mcp.json. Prefer the absolute path of node and set QODERCLI_PATH explicitly (nvm-managed binaries are often missing from the PATH seen by MCP child processes):

Proxy Support: To use your Qoder CLI proxy quota, add HTTP_PROXY and/or HTTPS_PROXY to the server's environment. When these are set at the MCP server level, they will be passed to all qodercli subprocesses.

添加到 ~/.qoder/mcp.json。建议使用 node 的绝对路径并显式设置 QODERCLI_PATH（MCP 子进程的 PATH 中经常缺少 nvm 管理的二进制目录）：

代理支持：要使用 Qoder CLI 代理额度，可在服务器的环境变量中添加 HTTP_PROXY 和/或 HTTPS_PROXY。当这些变量在 MCP 服务器级别设置时，它们会被传递到所有 qodercli 子进程。

{
  "mcpServers": {
    "qodercli-mcp": {
      "command": "npx",
      "args": ["-y", "qodercli-mcp"],
      "env": {
        "QODERCLI_PATH": "/absolute/path/to/qodercli",
        "PATH": "/usr/local/bin:/usr/bin:/bin"
      }
    },
    "qodercli-mcp-with-proxy": {
      "command": "npx",
      "args": ["-y", "qodercli-mcp"],
      "env": {
        "QODERCLI_PATH": "/absolute/path/to/qodercli",
        "HTTP_PROXY": "http://127.0.0.1:39900",
        "HTTPS_PROXY": "http://127.0.0.1:39900",
        "PATH": "/usr/local/bin:/usr/bin:/bin"
      }
    }
  }
}

Developers running a local checkout instead of the published package (Option B) should replace command/args with the absolute node path and /path/to/qodercli-mcp/src/index.js (nvm-managed node is often missing from the PATH seen by MCP child processes). 使用本地源码（方式 B）的开发者请将 command/args 换成 node 绝对路径与 /path/to/qodercli-mcp/src/index.js（MCP 子进程的 PATH 中经常缺少 nvm 管理的二进制目录）。

Claude Code / Claude Desktop

{
  "mcpServers": {
    "qodercli-mcp": {
      "command": "node",
      "args": ["/absolute/path/to/qodercli-mcp/src/index.js"],
      "env": {
        "QODERCLI_PATH": "/absolute/path/to/qodercli"
      }
    }
  }
}

Tool: ask-qoder

Structured output / 结构化输出

ask-qoder declares an MCP outputSchema and returns, in addition to the human-readable text, a structuredContent object:

ask-qoder 声明了 MCP outputSchema，除可读文本外还返回 structuredContent 对象：

{
  "session_id": "77826b5c-...",   // pass back as resume_session_id / 回传用于续接
  "content": "OK",
  "is_error": false,
  "exit_code": 0,
  "duration_ms": 1280,
  "total_credits": 0.53,
  "num_turns": 1,
  "timed_out": false,
  "truncated": false
}

Sandbox mapping / 沙箱映射

Explicit permission_mode or approval_policy always wins over sandbox. 显式设置的 permission_mode / approval_policy 优先于 sandbox。

Permission modes (verified semantics) / 权限模式（实测语义）

Tool: list-sessions

Lists local qodercli sessions (index, summary, session id) so a client can pick a resume_session_id. Takes no arguments.

列出本地 qodercli 会话（序号、摘要、会话 ID），便于挑选 resume_session_id。无参数。

Tool: list-models

Lists models currently supported by qodercli (via --list-models), so a client can pick a valid model value at runtime instead of relying on stale knowledge. Returns both a text list and a structured models array. Takes no arguments.

列出 qodercli 当前支持的模型，供运行时选择有效的 model 值（不依赖过时知识）。返回文本清单和结构化 models 数组。无参数。

Usage Examples / 使用示例

Example 1: Simple code explanation / 简单代码解释

{ "name": "ask-qoder", "arguments": { 
  "prompt": "Explain what main.py does",
  "cwd": "/path/to/project",
  "timeout_ms": 180000 
}}

结果会返回一段自然语言解释，帮助理解文件功能。

Example 2: Ask a second opinion / 获取第二意见

{ "name": "ask-qoder", "arguments": { 
  "prompt": "@src/service.py Review this file for security issues and suggest improvements",
  "model": "qwen-plus",
  "permission_mode": "dont_ask",
  "timeout_ms": 300000 
}}

Qoder 会给出安全建议和改进方案。

Example 3: Multi-turn conversation via resume / 多轮对话续接

// First call — session_id comes back in structuredContent
// 首次调用 —— session_id 会在 structuredContent 中返回
{ "name": "ask-qoder", "arguments": {
  "prompt": "Help me refactor this module to improve readability",
  "cwd": "/projects/backend",
  "timeout_ms": 300000 
}}
// Then reuse structuredContent.session_id:
// 然后把 structuredContent.session_id 回传：
{ "name": "ask-qoder", "arguments": {
  "prompt": "Now add error handling for database timeouts",
  "resume_session_id": "77826b5c-cd6b-4213-b423-d95b4e1deab0"
}}
// Or discover ids with list-sessions / 或用 list-sessions 查找历史会话 ID
{ "name": "list-sessions", "arguments": {} }

通过 resume_session_id 可实现多轮交互式迭代优化。

Example 4: Code review with specific focus / 针对性代码审查

{ "name": "ask-qoder", "arguments": {
  "prompt": "Analyze performance bottlenecks in utils.py",
  "model": "qwen-max",
  "permission_mode": "default",
  "output_format": "text",
  "timeout_ms": 240000 
}}

适合性能分析和优化建议场景。

Example 5: Read-only analysis / 只读分析

{ "name": "ask-qoder", "arguments": {
  "prompt": "Audit this codebase for security issues; do not modify anything",
  "cwd": "/workspaces/repo",
  "sandbox": "read-only",
  "timeout_ms": 300000 
}}

read-only 会禁用写文件与 shell 工具，适合审计/评审场景。

Example 6: Project-wide analysis / 项目范围分析

{ "name": "ask-qoder", "arguments": {
  "prompt": "Summarize the architecture of this project and identify key modules",
  "cwd": "/workspaces/repo",
  "timeout_ms": 420000,
  "model": "qwen-plus"
}}

适用于大型项目快速梳理和架构理解。

Best Practices / 最佳实践

1. Specify working directory — Always pass cwd when operating on a specific project 操作特定项目时务必指定 cwd

2. Use timeout protection — For complex prompts, set explicit timeout_ms shorter than 60min 复杂任务设置 timeout_ms（建议 5–10 分钟），避免挂起

3. Resume for multi-turn — Chain follow-ups via resume_session_id instead of repeating context 后续追问用 resume_session_id 续接会话，避免重复上下文

4. Model selection — Call list-models first to discover currently supported models; larger models are better for deep analysis 先调 list-models 查询当前可用模型；深度分析建议选择大模型

5. Permission mode — The server default is read-only (dont_ask); set QODERCLI_DEFAULT_PERMISSION_MODE=bypass_permissions to make full (YOLO) access the default for personal deployments. Per-call: tasks that must create/modify files need sandbox: "workspace-write"; shell access needs danger-full-access. Do not combine sandbox with an explicit permission_mode (the latter wins) 服务器默认只读（dont_ask）；个人部署可用 QODERCLI_DEFAULT_PERMISSION_MODE=bypass_permissions 将全开（YOLO）设为默认。单次调用：需要改文件设 sandbox: "workspace-write"，需要 shell 用 danger-full-access；勿与显式 permission_mode 混用（后者优先生效）

Environment variables / 环境变量

Development / 开发

npm test        # smoke test: protocol handshake + tool invocation
node src/index.js   # run the server manually (stdio)

Disclaimer / 免责声明

This is an unofficial, third-party tool. It is not affiliated with, endorsed, or sponsored by Qoder. Use permission_mode: bypass_permissions with care — delegated prompts may modify files in the target working directory.

本项目为非官方第三方工具，与 Qoder 官方无关。请谨慎使用 bypass_permissions 权限模式——委托的任务可能修改目标工作目录中的文件。

License

MIT