mcp-survey
Survey available MCP servers from a given repository URL and recommend which ones to add to the catalog
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Survey available MCP servers from a given repository URL and recommend which ones to add to the catalog
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
Read HANDOFF.md and continue from where we left off
Use when ending a session, completing a milestone, or stopping mid-task and context must be preserved for the next agent
Use when organizing raw content into slide-ready format, or when the user says "prepare slides", "structure this for a presentation", "brief for pptx".
Use when the user shares a URL or article and asks to extract key learnings, summarize topics, or generate a digest formatted for Google Chat, Slack, Discord, Telegram, or similar messaging tools. Accepts an optional format parameter.
Use when working with Kubernetes clusters, manifests, and related tasks.
Use when writing a CV, bio, LinkedIn post, or talk abstract for Silvio; when calibrating technical recommendations to Silvio's experience ("do I have experience with X?"); or when an introduction or speaker section is needed. Loads timeline, stack, credentials, and preferences on demand via the pointer table.
| name | mcp-survey |
| description | Survey available MCP servers from a given repository URL and recommend which ones to add to the catalog |
$ARGUMENTS is the URL of the MCP server registry to survey. Required — no default fallback.
Steps:
Fetch $ARGUMENTS and list all available MCP server packages.
Check prerequisites: run which uv uvx 2>&1; uv --version 2>&1; uvx --version 2>&1
curl -LsSf https://astral.sh/uv/install.sh | sh and stop.Load state from disk:
{"mcpServers": {}} if missing.mcp; may not exist).Analyze the current project context (CLAUDE.md, scripts, services, infrastructure) to identify technologies and services in active use.
For each server from the survey, classify it as one of:
mcp, no catalog changes needed.Present a table in two sections:
Ask the user which new servers to add. (Available ones need no action here.)
For each selected new server, fetch its README to get the exact package name and required env vars. Add to ~/.claude/mcp.catalog.json using this structure:
"server-name": {
"command": "uvx",
"args": ["--from", "package-name@latest", "server-command", "--any-safe-flags"],
"env": { "FASTMCP_LOG_LEVEL": "ERROR" }
}
Include only env vars that are required; leave the value empty ("") for secrets the user must fill in.
After updating the catalog, remind the user to run mcp to activate servers in the current project.
mcp \
--add mcp-server-name-1 \
--add mcp-server-name-2