home / skills / aaaaqwq / agi-super-skills / mcp-installer

mcp-installer skill

safe

This skill helps you locate MCP server tools on GitHub, extract npx commands, and update your ~/.claude.json with proper environment placeholders.

npx playbooks add skill aaaaqwq/agi-super-skills --skill mcp-installer

Review the files below or copy the command above to add this skill to your agents.

Files (1)

SKILL.md

2.5 KB

---
name: mcp-installer
description: 从GitHub搜索并自动安装配置MCP(Model Context Protocol)服务器工具到Claude配置文件。当用户需要安装MCP工具时触发此技能。工作流程：搜索GitHub上的MCP项目 -> 提取npx配置 -> 添加到~/.claude.json -> 处理API密钥（如有）。
---

# MCP工具安装助手

你是一个MCP工具安装助手，帮助用户从GitHub搜索并安装MCP服务器配置。

## 工作流程

### 1. 搜索阶段

1. 询问用户需要什么类型的MCP工具
2. 使用GitHub搜索功能查找相关项目
3. 搜索关键词格式：`mcp server` + 用户关键词，或者 `mcp-` + 关键词
4. 优先寻找官方ModelContextProtocol组织下的项目
5. 查找项目的README或文档，确认正确的npx安装命令

### 2. 配置提取

从项目文档中提取标准的npx配置格式：

**标准格式：**
```json
{
  "mcpServers": {
    "工具名": {
      "command": "npx",
      "args": ["-y", "包名@latest"]
    }
  }
}
```

**带环境变量的格式：**
```json
{
  "mcpServers": {
    "工具名": {
      "command": "npx",
      "args": ["-y", "包名@latest"],
      "env": {
        "API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}
```

### 3. 配置安装

1. 读取用户现有的`~/.claude.json`配置文件
2. 检查是否已存在同名MCP服务器配置
3. 将新配置添加到mcpServers字段中
4. 保持JSON格式正确，确保不破坏现有配置
5. 如果配置文件不存在，创建新文件

### 4. 密钥处理

- 如果MCP工具需要API密钥，明确告知用户
- 在配置中预留环境变量字段
- 用`YOUR_API_KEY_HERE`等占位符标注
- 提供获取密钥的指导链接或说明

### 5. 完成确认

配置完成后输出：

```
✅ MCP工具安装完成！

工具名称：[工具名]
项目地址：[GitHub URL]
配置位置：~/.claude.json

需要配置的密钥（如有）：
- [密钥名称]: [获取说明]

请重启Claude Code以加载新配置。
```

## 注意事项

- Windows用户配置文件位于：`%USERPROFILE%\.claude.json`
- macOS/Linux用户配置文件位于：`~/.claude.json`
- 处理JSON解析错误时，给出清晰的错误提示
- 如果GitHub搜索无结果，建议调整搜索关键词
- 对于复杂的配置（非简单npx），建议用户手动配置并提供指导

## 可用工具

- GitHub搜索：`mcp__github__search_repositories`
- GitHub获取文件内容：`mcp__github__get_file_contents`
- 读取配置文件：Read工具
- 写入配置文件：Write工具

Overview

This skill automates finding and installing MCP (Model Context Protocol) server tools from GitHub into a Claude configuration file. It locates relevant repositories, extracts npx installation commands and configuration snippets, and updates the user's ~/.claude.json (or %USERPROFILE%\.claude.json on Windows). It also flags required API keys and leaves clear placeholders and instructions.

How this skill works

The skill queries GitHub for MCP-related projects using targeted keywords and prioritizes the official ModelContextProtocol organization when available. It fetches README or docs to extract a standard npx-based configuration block, then reads the user’s Claude config, merges the new mcpServers entry safely, and writes the updated JSON back. If the tool requires credentials, the skill inserts env placeholders and supplies brief guidance on where to obtain keys.

When to use it

You want to add an MCP server tool to Claude without manual JSON editing.
You found an MCP project on GitHub and need its npx install configured quickly.
You need to ensure existing ~/.claude.json stays valid while adding a new server.
You want automated detection of required API keys and convenient placeholders.
You prefer prioritized search of ModelContextProtocol organization projects.

Best practices

Confirm the exact npx install command in the project README before applying.
Back up existing ~/.claude.json before automatic modifications.
Use descriptive tool names for the mcpServers key to avoid collisions.
Manually supply API keys after installation; the skill leaves secure placeholders.
If the project has complex setup beyond npx, follow manual installation guidance.

Example use cases

Search GitHub for an ‘mcp server’ implementation and auto-add its npx config to ~/.claude.json.
Add an MCP tool that needs an API key: skill adds env with YOUR_API_KEY_HERE and provides key acquisition notes.
Update a dev machine’s Claude config with a new MCP server while preserving existing entries.
Fallback guidance when search returns no hits: suggest alternate keywords and manual config steps.

FAQ

What if my ~/.claude.json is invalid JSON?

The skill reports precise JSON parse errors and suggests creating a backup or restoring a valid file before retrying.

How are API keys handled?

Required keys are not fetched automatically. The skill inserts env placeholders (e.g., YOUR_API_KEY_HERE) and provides brief instructions or links on where to get the key.