cli-jaw MCP工具 是 AI Skill Hub 本期精选MCP工具之一。综合评分 8.0 分,整体质量较高。我们强烈推荐将其纳入你的 AI 工具库,帮助提升工作效率。
cli-jaw MCP工具 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
cli-jaw MCP工具 是一款遵循 MCP(Model Context Protocol)标准协议的 AI 工具扩展。通过 MCP 协议,它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务,实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用,都可以通过自然语言在 AI 对话中直接触发,极大提升生产效率。
# 方式一:通过 Claude Code CLI 一键安装
claude skill install https://github.com/lidge-jun/cli-jaw
# 方式二:手动配置 claude_desktop_config.json
{
"mcpServers": {
"cli-jaw-mcp--": {
"command": "npx",
"args": ["-y", "cli-jaw"]
}
}
}
# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json
# 安装后在 Claude 对话中直接使用 # 示例: 用户: 请帮我用 cli-jaw MCP工具 执行以下任务... Claude: [自动调用 cli-jaw MCP工具 MCP 工具处理请求] # 查看可用工具列表 # 在 Claude 中输入:"列出所有可用的 MCP 工具"
// claude_desktop_config.json 配置示例
{
"mcpServers": {
"cli-jaw_mcp__": {
"command": "npx",
"args": ["-y", "cli-jaw"],
"env": {
// "API_KEY": "your-api-key-here"
}
}
}
}
// 保存后重启 Claude Desktop 生效
<p align="center"> <img src="docs/assets/readme/banner.jpg" alt="CLI-JAW — your personal AI agent. Every AI CLI, one dashboard." width="100%"> </p>
<p align="center"><b>One assistant, one memory, one dashboard for the AI coding CLIs you already pay for.</b><br> Claude, Codex, Cursor, Grok, Copilot, OpenCode, Kiro, Antigravity and Pi — working together as a team.</p>
<p align="center"> <a href="https://npmjs.com/package/cli-jaw"><img src="https://img.shields.io/npm/v/cli-jaw?color=cb3837&label=npm&logo=npm" alt="npm version"></a> <a href="https://github.com/lidge-ai/cli-jaw/releases/latest"><img src="https://img.shields.io/github/v/release/lidge-ai/cli-jaw?label=release" alt="latest release"></a> <img src="https://img.shields.io/badge/node-%3E%3D22.4-339933?logo=node.js&logoColor=white" alt="Node.js 22.4+"> <a href="LICENSE"><img src="https://img.shields.io/badge/license-MIT-blue" alt="MIT license"></a> </p>
```bash
curl -fsSL https://raw.githubusercontent.com/lidge-ai/cli-jaw/main/scripts/install-wsl.sh | bash source ~/.bashrc jaw dashboard bash "$(npm root -g)/cli-jaw/scripts/verify-fresh-install.sh"
From Windows PowerShell into WSL, run commands through a login shell so the WSL profile PATH is loaded:
powershell wsl.exe -d Ubuntu -- bash -lc "jaw dashboard"
</details>
<details>
<summary><b>Native Windows (PowerShell beta)</b> — detached server logs</summary>
`jaw serve` preserves the stdout and stderr streams it inherits and also appends
both streams to `<JAW_HOME>\logs\serve.log`. At startup, a file already at 5 MiB
is rotated once to `serve.log.1`. Native Windows still does not have a registered
`jaw service` logging backend. PowerShell's
`Start-Process -RedirectStandardOutput/-RedirectStandardError` creates or
truncates its target files on every launch, so do not point those options at
the instance-owned `serve.log`.
If separate operator-owned stdout/stderr files are needed, run the redirection
inside a child PowerShell process instead. This example appends them under
`<JAW_HOME>\logs` without the `Start-Process` truncate default:
powershell $jawHome = 'C:\jaw\worker-a' $port = 3458 $logDir = Join-Path $jawHome 'logs' $outLog = Join-Path $logDir 'serve.out.log' $errLog = Join-Path $logDir 'serve.err.log' New-Item -ItemType Directory -Force -Path $logDir -ErrorAction Stop | Out-Null foreach ($path in @($outLog, $errLog)) { # OpenOrCreate preserves existing content while proving that the child can append. $probe = [IO.File]::Open($path, 'OpenOrCreate', 'Write', 'ReadWrite') $probe.Dispose() }
$jaw = (Get-Command jaw.cmd -ErrorAction Stop).Source $childCommand = "& '$jaw' --home '$jawHome' serve --port $port --no-open 1>> '$outLog' 2>> '$errLog'" $encoded = [Convert]::ToBase64String([Text.Encoding]::Unicode.GetBytes($childCommand)) Start-Process -FilePath powershell.exe -ArgumentList '-NoProfile', '-EncodedCommand', $encoded -WindowStyle Hidden | Out-Null
Read each stream from a separate PowerShell terminal (`Get-Content -Wait`
occupies its terminal). These commands use explicit paths because variables
from the launch terminal are not available in a new PowerShell session:
powershell
npm install -g cli-jaw jaw dashboard ```
<p align="center"> <a href="https://github.com/lidge-ai/cli-jaw/releases/latest"><img src="https://img.shields.io/badge/macOS-.dmg-24292f?logo=apple&logoColor=white" alt="Download for macOS (.dmg)"></a> <a href="https://github.com/lidge-ai/cli-jaw/releases/latest"><img src="https://img.shields.io/badge/Windows-.exe-24292f?logo=windows&logoColor=white" alt="Download for Windows (.exe)"></a> <a href="https://github.com/lidge-ai/cli-jaw/releases/latest"><img src="https://img.shields.io/badge/Linux-.AppImage-24292f?logo=linux&logoColor=white" alt="Download for Linux (.AppImage)"></a> </p>
Install<details> <summary><b>Safe install</b> — for existing users who want minimal changes</summary> ```bash macOS / Linux / WSL with Node.js 22+ already installednpm install -g cli-jaw jaw dashboard bash > npm install -g cli-jaw --allow-scripts=cli-jaw > powershell npm install -g cli-jaw --allow-scripts=cli-jaw npm config set allow-scripts=cli-jaw --location=user jaw doctor powershell Set-ExecutionPolicy -Scope CurrentUser RemoteSigned jaw.cmd doctor node "$(npm prefix -g)\node_modules\cli-jaw\dist\bin\cli-jaw.js" doctor bash curl -fsSL https://raw.githubusercontent.com/lidge-ai/cli-jaw/main/scripts/install.sh | bash source "${ZDOTDIR:-$HOME}/.zshrc" 2>/dev/null || true bash "$(npm root -g)/cli-jaw/scripts/verify-fresh-install.sh" powershell
1. Install WSL (PowerShell as Admin)wsl --install bash
PABCD: plan, audit, build, check, doneFor complex tasks CLI-JAW runs a structured workflow. You approve every transition; read-only workers verify the plan and the result.
State survives restarts. Start with Free options (no credit card needed)copilot login # GitHub Copilot (free tier available) opencode # OpenCode — free models available kiro # AWS Kiro (free tier with AWS account) Employees: your CLI calls the othersYou talk to one AI (the "Boss"). When it needs specialized work, it dispatches tasks to employees — each running its own CLI and model — and reviews their output before answering you.
Agents and workflowjaw employee list jaw dispatch --agent "Backend" --task "..." --watch jaw orchestrate # PABCD workflow jaw goal status # persistent goals Troubleshooting
---
🎯 aiskill88 AI 点评
A 级
2026-05-20
设计简洁高效,多引擎支持提供灵活选择。代码质量好,维护活跃。适合开发者快速集成AI能力。 📚 实用指南(长尾问题)
适合谁
最佳实践
常见错误
部署方案
⚡ 核心功能
👥 适合谁
⭐ 最佳实践
⚠️ 常见错误
👥 适合人群🎯 使用场景
⚖️ 优点与不足✅ 优点
⚠️ 不足
⚠️ 使用须知
AI Skill Hub 为第三方内容聚合平台,本页面信息基于公开数据整理,不对工具功能和质量作任何法律背书。 建议在沙箱或测试环境中充分验证后,再部署至生产环境,并做好必要的安全评估。 📄 License 说明
✅ MIT 协议 — 最宽松的开源协议之一,可自由商用、修改、分发,仅需保留版权声明。 🔗 相关工具推荐📚 相关教程推荐 📰 相关 AI 新闻
🍿 AI 圈相关吃瓜
🧩 你可能还需要
基于当前 Skill 的能力图谱,自动补全的工具组合
❓ 常见问题 FAQ支持Claude、Codex、Gemini、OpenAI等5个主流引擎,可自由切换。
💡 AI Skill Hub 点评
经综合评估,cli-jaw MCP工具 在MCP工具赛道中表现稳健,质量优秀。如果你已有明确的使用需求,可以直接上手体验;如果还在评估阶段,建议对比同类工具后再做决策。 🌐 原始信息
🔗 原始来源
🐙 GitHub 仓库 https://github.com/lidge-jun/cli-jaw
🌐 官方网站 https://lidge-jun.github.io/cli-jaw/
收录时间:2026-05-16 · 更新时间:2026-05-19 · License:MIT · AI Skill Hub 不对第三方内容的准确性作法律背书。 🤖 交给 Agent 安装 · cli-jaw MCP工具选择 Agent 类型,复制安装指令后粘贴到对应客户端 claude skill install https://github.com/lidge-jun/cli-jaw
|