mcpick

MCPAI代理

提供方 spences10 · 包名 mcpick

AI代理 stdio · 本地进程 未标注 社区 / 第三方 Claude DesktopCursorClineClaude Code
查看接入方式

Claude Code extension manager — MCP servers, plugins (skills, hooks, agents), and marketplaces

一句话选型结论

按资料字段整理

mcpick 属于AI代理类 MCP 服务器,stdio · 本地进程,鉴权方式未标注,可直接接入 Claude Desktop、Cursor、Cline 等,有可直接执行的安装命令。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式stdio · 本地进程 鉴权未标注 部署方式本地部署
GitHub 星标 67 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

mcpickanthropicclaude

安装与配置

stdio · 本地进程 未标注
客户端在本机拉起子进程,数据不出本机
npx -y mcpick

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    stdio 服务在本地起进程,需要先装好 Cross-platform,再按安装命令拉取依赖。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Cursor、Cline,换客户端不用重新研究配置。

先想清楚的地方

  • stdio 方式要求本地装好运行时(如 Node.js),换机器要重新装一遍。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 完全不想在本地装环境的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
mcpick当前 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方spences10上游标注的维护方 spences10
分类AI代理本站按上游分类展示
连接方式stdio · 本地进程客户端在本机拉起子进程,数据不出本机
鉴权方式未标注远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时mcpick · Cross-platform本地安装时用到的包标识与运行时
部署类型本地部署上游给出的部署形态
最近核验2026-04-11上游最后核验时间

详细介绍

9.1 KB
来自项目仓库与上游目录的原文,未做删改

MCPick

Vendor-neutral MCP configuration manager with first-class Claude Code
support.

MCPick helps humans and LLM agents inspect, toggle, and back up MCP
server configuration across multiple AI clients. Claude Code-specific
plugins, hooks, marketplaces, and cache commands remain available, but
they are no longer the core product model.

Install```bash

npm install -g mcpick

or run without installing

npx mcpick --help


Requirements:

- Node.js 22+
- Claude Code is required only for Claude Code-specific commands
- The GitHub CLI (`gh`, authenticated) is required for portable skills
  commands; check-skills
  validates skills before install when available

## Agent-first CLI

In non-TTY environments, MCPick shows help instead of launching the
interactive TUI. This makes it safer for prompts like:

> “Use mcpick to work out how to enable this MCP server.”

Start with:```bash
npx mcpick --help
npx mcpick clients
npx mcpick list --json

MCPick redacts known secret patterns before printing output. MCP
configs often contain env vars and authorization headers, so env and
headers values are shown as *** in JSON output.

MCP server mode

npx mcpick serve runs MCPick itself as an MCP server over stdio, so
agents can manage MCP configuration through tool calls instead of
shelling out to the CLI. Tools:

  • Read: mcpick_list, mcpick_clients, mcpick_get, mcpick_doctor
  • Mutate: mcpick_enable, mcpick_disable, mcpick_remove,
    mcpick_add, mcpick_add_json

Read-only/destructive annotations are set so clients can make safe
decisions; secret warnings and from_env resolution behave the same
as the CLI. Client config example:```json
{
"mcpServers": {
"mcpick": {
"command": "npx",
"args": ["-y", "mcpick", "serve"]
}
}
}


## MCP clients

Supported client adapters:

| Client                | Scopes               | Command examples                                  |
| --------------------- | -------------------- | ------------------------------------------------- |
| Claude Code           | local, project, user | `mcpick list`, `mcpick enable `           |
| Claude Desktop        | user                 | `mcpick list --client claude-desktop`             |
| Codex CLI             | user                 | `mcpick list --client codex`                      |
| Gemini CLI            | project, user        | `mcpick list --client gemini-cli --scope project` |
| VS Code / Copilot     | project              | `mcpick list --client vscode --scope project`     |
| Cursor                | project, user        | `mcpick list --client cursor --scope user`        |
| Windsurf              | user                 | `mcpick list --client windsurf --scope user`      |
| OpenCode              | project, user        | `mcpick list --client opencode --scope project`   |
| Pi via pi-mcp-adapter | project, user        | `mcpick list --client pi --scope user`            |

Show known config locations:```bash
npx mcpick clients
npx mcpick clients --json

MCP server commands```bash

List Claude Code registry/status

npx mcpick list
npx mcpick list --json

List another client

npx mcpick list --client pi --scope user --json
npx mcpick list --client opencode --scope project

Claude Code enable/disable

npx mcpick enable <server> --scope local
npx mcpick disable <server> --scope local

Add/remove Claude Code server definitions

npx mcpick add --name <server> --command npx --args "-y,package-name"
npx mcpick add --from-registry io.github.user/server
npx mcpick add-json <name> '{"command":"npx","args":["-y","package-name"]}'
npx mcpick remove <server>


`add --from-registry` requires an exact official MCP Registry name and
writes the package&#x27;s exact published version. It currently supports
npm packages using stdio; unsupported package types fail without
writing a guessed configuration. Registry-declared required
environment variables must be supplied with `--from-env` or `--env`.
`--dry-run` works for adapter-backed clients.

MCPick warns when a value you write looks like a secret, redacts
printed output, and `npx mcpick doctor` flags plaintext secrets
already on disk. To keep secrets off the command line and out of LLM
conversation context, resolve them from the process environment:```bash
pnpx nopeek run .env --only GITHUB_TOKEN -- npx mcpick add --name github --command npx --args &quot;-y,@modelcontextprotocol/server-github&quot; --from-env GITHUB_TOKEN --yes

MCP client config files may still store secrets in plain text because
that is how many clients currently load MCP credentials; prefer
${VAR} references where your client supports them.

Validate your setup

npx mcpick doctor checks every known client config: JSON validity,
per-client schema shape, missing commands on PATH, duplicate servers
across scopes, plaintext secrets, and unpinned server packages. It
exits non-zero when it finds errors, so it works in CI:```bash
npx mcpick doctor
npx mcpick doctor --client cursor --json


## Portable skills

MCPick installs portable SKILL.md packs through the GitHub CLI&#x27;s
`gh skill` commands. Installs are staged in a temporary directory and
validated with check-skills before anything is written to your agent
directories, and each install records provenance (source repo, pinned
ref, target agents) shown in `skills list --json`.```bash
# List installed skills for a client
npx mcpick skills list --agent pi --json

# Search GitHub, or see what a source offers without installing
npx mcpick skills search svelte
npx mcpick skills add spences10/skills --list
npx mcpick skills preview spences10/skills svelte-runes

# Install one skill, pinned for reproducibility
npx mcpick skills add spences10/skills --agent pi --skill svelte-runes --pin v1.2.0 --yes

# Install all skills from a repo at user scope
npx mcpick skills add spences10/skills --agent opencode --all --global --yes

# Check for updates, then apply them
npx mcpick skills update --dry-run --json
npx mcpick skills update

skills remove is not supported by the gh skill backend; it reports
the manual deletion paths instead.

Claude Code-specific tools

These commands wrap Claude Code concepts and are intentionally
client-specific:```bash

Plugins

npx mcpick plugins list
npx mcpick plugins install <name>@<marketplace>
npx mcpick plugins enable <name>@<marketplace>
npx mcpick plugins disable <name>@<marketplace>

Marketplaces

npx mcpick marketplace list
npx mcpick marketplace add <source>
npx mcpick marketplace update
npx mcpick marketplace remove <name>

Hooks and plugin cache

npx mcpick hooks list
npx mcpick cache status
npx mcpick cache refresh


## Profiles and backups

Profiles are portable MCP server snapshots. Claude Code plugin state
is preserved as optional Claude-specific profile metadata.```bash
# Legacy Claude Code shortcuts still work
npx mcpick --profile database
npx mcpick --save-profile mysetup
npx mcpick --list-profiles

# Save/load profiles for a specific MCP client
npx mcpick profile save work --client vscode --scope project
npx mcpick profile load work --client opencode --scope project
npx mcpick profile load work --client pi --scope user

npx mcpick backup
npx mcpick restore [file]

# Safe-write rollback backups created before config mutations
npx mcpick rollback --list
npx mcpick rollback [file]

Interactive TUI

Running npx mcpick in a terminal launches the human-facing menu:```text
MCPick - MCP Configuration Manager

What would you like to do?
Enable / Disable MCP servers
Validate configs (doctor)
Skills
Client-specific tools
Load profile
Save profile
Backup config
Restore from backup
Exit


The primary TUI flow is client-first: choose a client, then toggle its
MCP servers. Claude Code plugins, hooks, marketplaces, and cache live
under “Client-specific tools”. “Validate configs (doctor)” runs the
same read-only health checks as `mcpick doctor` (config parse errors,
schema-shape issues, missing commands, duplicate servers, plaintext
secrets, unpinned servers) and prints the report grouped by client.

## Config locations

MCPick reads the standard locations used by each client adapter.
Common paths include:

| Path                     | Purpose                                         |
| ------------------------ | ----------------------------------------------- |
| `~/.claude.json`         | Claude Code local/user MCP config               |
| `.mcp.json`              | Shared project MCP config                       |
| `.gemini/settings.json`  | Gemini CLI project config                       |
| `.vscode/mcp.json`       | VS Code / Copilot project config                |
| `.cursor/mcp.json`       | Cursor project config                           |
| `opencode.json`          | OpenCode project config                         |
| `~/.config/mcp/mcp.json` | Shared global MCP config used by pi-mcp-adapter |
| `.pi/mcp.json`           | Pi project override                             |

MCPick-owned state lives under `$XDG_CONFIG_HOME/mcpick/`
(`~/.config/mcpick/` by default; override with `MCPICK_CONFIG_DIR`).
State previously kept in `~/.claude/mcpick/` is moved there
automatically on first run.

## Development```bash
pnpm install
pnpm test
pnpm run check
pnpm build

See docs/VENDOR_NEUTRAL_ARCHITECTURE.md for architecture notes.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
mcpick 怎么安装?

在客户端按下面的安装命令接入:npx -y mcpick。对应的包名是 mcpick。装完在客户端配置里引用同一个包或端点。

mcpick 怎么在 Claude Desktop、Cursor、Cline 里配置?

它的传输方式是stdio · 本地进程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

mcpick 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

mcpick 需要 API Key 吗?

资料没有标注鉴权方式,是否需要密钥取决于服务本身,接入前按官方文档确认。

mcpick 支持哪些客户端?

资料标注支持 Claude Desktop、Cursor、Cline、Claude Code;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

mcpick 能提供哪些能力?

资料显示能力标签包括 mcpick、anthropic、claude、claude-code、cli。具体工具清单以官方文档为准。

mcpick 需要什么运行环境?

运行时为 Cross-platform;属于本地进程,需要在本机装好运行环境。

mcpick 是本地还是远程?

它是本地进程(stdio),由客户端在本机拉起。传输方式为stdio · 本地进程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-04-11。