agentleFS
xiaolaixiaolai/vmark/.claude/skills/mcp-server-manager/SKILL.md

mcp-server-manager

Skill851 starsChanged 29 days agoISCView on GitHub

Discover, register, and verify MCP servers. Use when a user asks to connect/add/install/remove an MCP server, or when you need to manage project MCP configuration.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check project .mcp.json for existing server configs.

    line 11
  2. Very specific:

    Check ~/.claude.json for global MCP servers (Claude Code).

    line 12
  3. Distinctive:

    When multiple sources define the same name, confirm which to use.

    line 39

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

MCP Server Manager

Workflow

  1. Discover candidate servers
    • Check project .mcp.json for existing server configs.
    • Check ~/.claude.json for global MCP servers (Claude Code).
    • Scan for MCP-related packages in package.json or Cargo.toml.
  2. Choose a registration target
    • Project-local: edit .mcp.json directly.
    • Global (Claude Code): use claude mcp add / claude mcp remove.
  3. Register the server
    • stdio server:
      claude mcp add <name> -- <command> <args...>
    • stdio with env:
      claude mcp add <name> -e KEY=VALUE -- <command> <args...>
    • Or edit .mcp.json directly for project-local config.
  4. Verify registration
    • For .mcp.json: read the file and confirm the entry exists.
    • For global: run claude mcp list to verify.
  5. Explain reload requirement
    • MCP servers are loaded at session start; ask the user to restart the session.

Notes

  • Infer type from config: url key = HTTP, command/args keys = stdio.
  • When multiple sources define the same name, confirm which to use.
  • For stdio servers using npx, the package downloads when the server first runs.

VMark Example

// .mcp.json
{
  "mcpServers": {
    "tauri": {
      "command": "npx",
      "args": ["-y", "@hypothesi/tauri-mcp-server"]
    }
  }
}

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.