mcp-survey

Stars0

Forks0

UpdatedApril 23, 2026 at 22:19

Survey available MCP servers from a given repository URL and recommend which ones to add to the catalog

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Source

smsilva

smsilva/linux

View GitHub Repository View Creator Repositories

Download

Related occupationsSOC

Based on SOC occupation classification

Computer Systems AnalystsComputer and Mathematical Occupations·SOC 15-1211

SKILL.md

readonly

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
- If uv/uvx are missing, tell the user to run curl -LsSf https://astral.sh/uv/install.sh | sh and stop.
Load state from disk:
- Global catalog: ~/.claude/mcp.catalog.json — create {"mcpServers": {}} if missing.
- Active servers: .mcp.json in current dir (written by mcp; may not exist).
- Known = all keys in global catalog. Active = all keys in .mcp.json.
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:
- active: already in .mcp.json — skip entirely.
- available: in global catalog but not in .mcp.json — can be enabled with mcp, no catalog changes needed.
- new: not in global catalog — needs to be fetched and added.
Present a table in two sections:
- "Available (run mcp to enable)": name | reason relevant
- "New — not yet in catalog": name | reason relevant | suggested safe flags (e.g. --readonly) Omit active servers. Sort each section by relevance to the project.
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
```

More from this repository

same repository

handoff-continue

smsilva/linux

Read HANDOFF.md and continue from where we left off

2026-06-230

handoff

smsilva/linux

Use when ending a session, completing a milestone, or stopping mid-task and context must be preserved for the next agent

2026-06-230

presentation-prep

smsilva/linux

Use when organizing raw content into slide-ready format, or when the user says "prepare slides", "structure this for a presentation", "brief for pptx".

2026-06-160

article-digest

smsilva/linux

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.

2026-06-120

kubernetes

smsilva/linux

Use when working with Kubernetes clusters, manifests, and related tasks.

2026-06-070

about-me

smsilva/linux

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.

2026-05-290

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
- If uv/uvx are missing, tell the user to run curl -LsSf https://astral.sh/uv/install.sh | sh and stop.
Load state from disk:
- Global catalog: ~/.claude/mcp.catalog.json — create {"mcpServers": {}} if missing.
- Active servers: .mcp.json in current dir (written by mcp; may not exist).
- Known = all keys in global catalog. Active = all keys in .mcp.json.
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:
- active: already in .mcp.json — skip entirely.
- available: in global catalog but not in .mcp.json — can be enabled with mcp, no catalog changes needed.
- new: not in global catalog — needs to be fetched and added.
Present a table in two sections:
- "Available (run mcp to enable)": name | reason relevant
- "New — not yet in catalog": name | reason relevant | suggested safe flags (e.g. --readonly) Omit active servers. Sort each section by relevance to the project.
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
```