MCP工具链
经 AI Skill Hub 精选评估，MCP工具链 获评「强烈推荐」。这款MCP工具在功能完整性、社区活跃度和易用性方面表现出色，AI 评分 8.0 分，适合有一定技术背景的用户使用。
📚 深度解析
通过安装 MCP工具链，你的 AI 助手将获得额外的工具调用能力，可以用自然语言直接操控该工具的功能，无需学习复杂的命令行语法。MCP 工具的核心价值在于"一次配置，永久增强"——配置完成后，每次与 AI 对话时都可以无缝调用这些工具。
在技术实现上，MCP 工具通过标准的 JSON-RPC 协议与 AI 客户端通信，工具的功能以"工具列表"的形式暴露给 AI 模型，AI 可以按需调用。MCP工具链 提供了结构化的工具调用接口，使 AI 模型能够精确地理解和使用每个功能点，显著降低 AI 在工具使用上的错误率。
与传统的 API 集成相比，MCP 工具的优势在于无需编写代码——用户只需在配置文件中添加几行 JSON，即可让 AI 获得全新能力。AI Skill Hub 将 MCP工具链 评为 AI 评分 8.0 分，属于同类工具中的优质选择。
📋 工具概览
MCP工具链 是一款遵循 MCP（Model Context Protocol）标准协议的 AI 工具扩展。通过 MCP 协议，它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务，实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用，都可以通过自然语言在 AI 对话中直接触发，极大提升生产效率。
📖 中文文档
MCP工具链 是一款遵循 MCP（Model Context Protocol）标准协议的 AI 工具扩展。通过 MCP 协议，它可以让 Claude、Cursor 等主流 AI 客户端直接访问和操作外部工具、数据源和服务，实现 AI 能力的无缝扩展。无论是文件操作、数据库查询还是 API 调用，都可以通过自然语言在 AI 对话中直接触发，极大提升生产效率。
- 通过标准 MCP 协议与 Claude、Cursor 等主流 AI 客户端深度集成
- 提供结构化工具调用接口，显著降低 AI 集成复杂度
- 支持 Claude Desktop 和 Claude Code 无缝接入，开箱即用
- 可与其他 MCP 工具组合叠加，构建完整 AI 工作站
- 轻量无侵入设计，不影响现有系统架构
- 在 Claude Desktop 对话中直接调用本地工具，实现 AI 与系统的深度联动
- 通过自然语言驱动复杂的多步骤自动化任务，代替繁琐手动操作
- 将多个 MCP 工具组合使用，构建个人专属 AI 工作站
# 方式一：通过 Claude Code CLI 一键安装
claude skill install https://github.com/phnx-labs/agents-cli
# 方式二：手动配置 claude_desktop_config.json
{
"mcpServers": {
"mcp---": {
"command": "npx",
"args": ["-y", "agents-cli"]
}
}
}
# 配置文件位置
# macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
# Windows: %APPDATA%/Claude/claude_desktop_config.json
- 确认已安装 Node.js（v18 或以上版本）
- 打开 Claude Desktop 或 Claude Code 的 MCP 配置文件
- 按「交给 Agent 安装 → Claude Desktop」标签中的 JSON 配置填入 mcpServers 字段
- 保存配置文件并重启 Claude 客户端
- 重启后，在对话中即可使用本工具
# 安装后在 Claude 对话中直接使用 # 示例： 用户: 请帮我用 MCP工具链 执行以下任务... Claude: [自动调用 MCP工具链 MCP 工具处理请求] # 查看可用工具列表 # 在 Claude 中输入："列出所有可用的 MCP 工具"
// claude_desktop_config.json 配置示例
{
"mcpServers": {
"mcp___": {
"command": "npx",
"args": ["-y", "agents-cli"],
"env": {
// "API_KEY": "your-api-key-here"
}
}
}
}
// 保存后重启 Claude Desktop 生效
简介
<p align="center"> <img src="assets/logo.png" alt="agents" width="120" /> </p>
agents
<p align="center"> <a href="https://www.npmjs.com/package/@phnx-labs/agents-cli"><img src="https://img.shields.io/npm/v/@phnx-labs/agents-cli.svg?style=flat-square" alt="npm version" /></a> <a href="./LICENSE"><img src="https://img.shields.io/npm/l/@phnx-labs/agents-cli.svg?style=flat-square" alt="license" /></a> <a href="https://www.npmjs.com/package/@phnx-labs/agents-cli"><img src="https://img.shields.io/npm/dm/@phnx-labs/agents-cli.svg?style=flat-square" alt="downloads" /></a> <a href="https://github.com/phnx-labs/agents-cli"><img src="https://img.shields.io/badge/github-phnx--labs%2Fagents--cli-blue?style=flat-square" alt="github" /></a> </p>
The missing toolchain for CLI coding agents. Run any agent on your existing subscription. Spawn parallel teams in isolated terminals. Schedule routines, drive browsers and Electron apps, and store secrets behind Touch ID — all from one CLI.
<p align="center"> <a href="https://github.com/anthropics/claude-code" title="Claude Code"><img src="assets/harnesses/anthropic.svg" height="32" alt="Claude Code" /></a> <a href="https://github.com/openai/codex" title="Codex CLI"><img src="assets/harnesses/openai.svg" height="32" alt="Codex CLI" /></a> <a href="https://github.com/google-gemini/gemini-cli" title="Gemini CLI"><img src="assets/harnesses/google.svg" height="32" alt="Gemini CLI" /></a> <a href="https://cursor.com" title="Cursor"><img src="assets/harnesses/cursor.svg" height="32" alt="Cursor" /></a> <a href="https://github.com/sst/opencode" title="OpenCode"><img src="assets/harnesses/opencode.png" height="32" alt="OpenCode" /></a> <a href="https://github.com/openclaw/openclaw" title="OpenClaw"><img src="assets/harnesses/openclaw.svg" height="36" alt="OpenClaw" /></a> <a href="https://github.com/NousResearch/hermes-agent" title="Hermes Agent"><img src="assets/harnesses/hermes.png" height="32" alt="Hermes Agent" /></a> <a href="https://x.ai" title="Grok Build (xAI)"><strong>Grok</strong></a> <a href="https://factory.ai" title="Factory AI Droid"><strong>Droid</strong></a> </p>
https://agents-cli.sh/demo.mp4
```bash npm install -g @phnx-labs/agents-cli
What's the relationship to Phoenix Labs / Rush?
agents-cli is an open client maintained by Phoenix Labs. Rush is a separate product. No Rush account required, no upsell.
Install from GitHub or local
agents workflows add gh:yourteam/code-review agents workflows add ./my-workflow
A workflow is a directory:
`WORKFLOW.md`'s Markdown body is the orchestrator's system prompt. Files under `subagents/` get copied to `~/.claude/agents/` at run time so the built-in Agent tool can dispatch to them by name — including in parallel. `skills/` and `plugins/` sync into the version home just for the run.
Install from a git URL or local path
agents plugins install hivemind@https://github.com/activeloopai/hivemind.git agents plugins install ./my-plugin
First run: omit --profile and we auto-pick the first installed Chromium-family
Chrome > Chromium > Brave > Edge; Windows prefers Edge (always preinstalled) >
Portable setup
```bash
Installs CLIs, registers MCP servers, syncs skills/commands/rules/hooks,
What gets logged (example event):
{ "ts": "2026-05-09T10:23:45Z", "event": "agent.run.end", "agent": "claude", "version": "2.1.121", "prompt": "Fix the auth bug in...", # truncated to 200 chars "durationMs": 45230, "exitCode": 0, "hostname": "your-mac", "platform": "darwin" } ```
What's logged: Operation type, agent, version, timing, prompt length + SHA-256 hash (raw text never stored), exit codes, errors, and secret bundle/key names with caller context. Argv entries that look like tokens or secret paths are redacted. What's NOT logged: Raw prompts, outputs, file contents, or secret values.
Permissions: Logs directory is 0700 (owner-only), files are 0600. Only you can read them.
Retention: 7 days by default, then auto-pruned.
Opt out: Set AGENTS_DISABLE_EVENT_LOG=1 in your shell to disable completely.
One config, every agent
```bash
Claude Code hits a rate limit -> Codex picks up automatically. Same project, same config.
agents run claude "refactor auth module" --mode edit --fallback codex,gemini ```
API keys in Keychain, not in .env files.
agents secrets create prod-stripe agents secrets add prod-stripe STRIPE_SECRET_KEY # Prompts, stores in Keychain agents secrets add prod-stripe TEST_CARD --value "4242..."
sets up shims, configures defaults. Done.
agents repo push # Snapshot your config to git ```
How config is layered
Two repos with the same shape, different roles:
| Repo | Role | Owner |
|---|---|---|
~/.agents-system/ | **System repo** — core/built-in skills, commands, hooks, rules, MCP configs, permissions, and profiles that ship with agents-cli. The defaults every install gets. | Maintained upstream at [phnx-labs/.agents-system](https://github.com/phnx-labs/.agents-system) |
~/.agents/ | **User repo** — your personal additions and overrides. This is what agents repo push/pull syncs. | You |
Version pinning: agents.yaml at project root pins which agent version to use (like .nvmrc for Node).
Resource resolution: When syncing resources (commands, skills, rules, hooks, MCP, permissions), the order is project > user > system. A .agents/ directory at project root wins, then ~/.agents/, then ~/.agents-system/. Same-named resources higher in the chain override lower ones; everything else unions in.
See docs/00-concepts.md for the full mental model: DotAgents repos, resource kinds, and how resolution works end-to-end.
Other useful commands: agents doctor checks CLI availability and resource sync drift, agents usage shows available quota/rate-limit data for installed agents, agents import adopts an existing unmanaged install, agents trash lists and restores soft-deleted version directories, and agents subagents installs reusable subagent definitions for parent-agent workflows.
---
What happens to my config when I switch versions?
Each version has its own isolated config directory. Switching just repoints a symlink — your per-version config stays untouched. On first migration (if you had a real ~/.claude/ directory before using agents-cli), that gets backed up once to ~/.agents-system/backups/.
agents-cli features (not agent-native resources)
| Agent | Routines | Teams | Session index |
|---|---|---|---|
| Claude Code | yes | yes | yes |
| Codex CLI | yes | yes | yes |
| Gemini CLI | yes | yes | yes |
| Cursor | -- | yes | -- |
| OpenCode | -- | yes | -- |
| Grok Build | -- | yes | yes |
| Antigravity | -- | yes | -- |
| Copilot | -- | -- | yes |
| OpenClaw, Amp, Kiro, Goose, Roo | -- | -- | -- |
Do agents use API keys or subscriptions?
Your choice. We hand off to the original CLI process — use your existing subscription or API key. This is intentional: subscription pricing is usually cheaper than API token pricing for individual users. Configure each agent however you want.
Does it store my API keys or send telemetry?
No CLI telemetry or phone-home. API keys come from your shell environment or each agent CLI's existing auth, and remote calls only happen when you invoke a feature that requires them, such as cloud dispatch.
For full transparency: agents-cli keeps a local event log at ~/.agents/.cache/logs/ so you can see exactly what agents did on your machine. Logs are owner-readable only (0600) and auto-prune after 7 days. Set AGENTS_DISABLE_EVENT_LOG=1 to disable. See Security & Privacy for details.
Workflows
Bundle an orchestrator prompt with optional subagents, skills, and plugins into a named, reusable pipeline. One bundle, one invocation.
```bash
Use a workflow — workflow name goes in the agent slot
agents run code-review "review PR #42 on acme/api"
WORKFLOW.md frontmatter
--- name: Code Review description: Evidence-grounded PR review with file:line citations. model: opus tools: - Read - Grep - Bash - WebFetch --- ```
Workflows that need to write — post PR comments, edit files, send Slack — should run with --mode edit or --mode full. agents run defaults to --mode plan (read-only), which deadlocks at ExitPlanMode in headless runs.
Resolution is project > user > system: a <repo>/.agents/workflows/<name>/ overrides a same-named workflow in ~/.agents/workflows/. Commit project workflows with your repo so teammates get the same pipeline.
---
Plugins
Bundle skills, commands, hooks, MCP servers, settings, and permissions under a single manifest. One source dir at ~/.agents/plugins/<name>/, mirrored into every installed Claude / OpenClaw version automatically.
```bash
Hooks-bearing plugins copy in but stay disabled by default
agents plugins install hivemind@https://github.com/activeloopai/hivemind.git \ --allow-exec-surfaces
FAQ
高质量的MCP工具链，易于使用
⚡ 核心功能
- 通过标准 MCP 协议与 Claude、Cursor 等主流 AI 客户端深度集成
- 提供结构化工具调用接口，显著降低 AI 集成复杂度
- 支持 Claude Desktop 和 Claude Code 无缝接入，开箱即用
- 可与其他 MCP 工具组合叠加，构建完整 AI 工作站
- 轻量无侵入设计，不影响现有系统架构
👥 适合人群
🎯 使用场景
- 在 Claude Desktop 对话中直接调用本地工具，实现 AI 与系统的深度联动
- 通过自然语言驱动复杂的多步骤自动化任务，代替繁琐手动操作
- 将多个 MCP 工具组合使用，构建个人专属 AI 工作站
⚖️ 优点与不足
- +MIT 协议，可免费商用
- +标准化 MCP 协议，生态互联性强
- +与 Claude 官方生态无缝对接
- +即插即用，配置简单快捷
- −依赖 Claude 客户端，非 Claude 用户无法使用
- −MCP 协议仍在持续演进，接口可能变更
- −需要一定的配置步骤
AI Skill Hub 为第三方内容聚合平台，本页面信息基于公开数据整理，不对工具功能和质量作任何法律背书。
建议在沙箱或测试环境中充分验证后，再部署至生产环境，并做好必要的安全评估。
✅ MIT 协议 — 最宽松的开源协议之一，可自由商用、修改、分发，仅需保留版权声明。
🔗 相关工具推荐
❓ 常见问题 FAQ
AI Skill Hub 点评：MCP工具链 的核心功能完整，质量优秀。对于Claude Desktop / Claude Code 用户来说，这是一个值得纳入个人工具库的选择。建议先在非生产环境试用，再逐步推广。
| 原始名称 | agents-cli |
| 原始描述 | 开源MCP工具：The missing toolchain for CLI coding agents. Run any agent on your subscription.。⭐8 · TypeScript |
| Topics | mcpai-agentsclitypescript |
| GitHub | https://github.com/phnx-labs/agents-cli |
| License | MIT |
| 语言 | TypeScript |
收录时间：2026-06-24 · 更新时间：2026-06-24 · License：MIT · AI Skill Hub 不对第三方内容的准确性作法律背书。