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
- Very specific: line 11
Check project .mcp.json for existing server configs.
- Very specific: line 12
Check ~/.claude.json for global MCP servers (Claude Code).
- Distinctive: line 39
When multiple sources define the same name, confirm which to use.
≈ “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.
Files
MCP Server Manager
Workflow
- Discover candidate servers
- Check project
.mcp.jsonfor existing server configs. - Check
~/.claude.jsonfor global MCP servers (Claude Code). - Scan for MCP-related packages in
package.jsonorCargo.toml.
- Check project
- Choose a registration target
- Project-local: edit
.mcp.jsondirectly. - Global (Claude Code): use
claude mcp add/claude mcp remove.
- Project-local: edit
- 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.jsondirectly for project-local config.
- stdio server:
- Verify registration
- For
.mcp.json: read the file and confirm the entry exists. - For global: run
claude mcp listto verify.
- For
- Explain reload requirement
- MCP servers are loaded at session start; ask the user to restart the session.
Notes
- Infer type from config:
urlkey = HTTP,command/argskeys = 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"]
}
}
}Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- tdimino/claude-code-minoan★ 41same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-coding-agentsSkill
- css-design-tddSkill
- mcp-devSkill
- plan-auditSkill
- planningSkill
- plan-verifySkill
- react-app-devSkill
- release-gateSkill
- rust-tauri-backendSkill
- shortcut-auditSkill
- tauri-app-devSkill
- tauri-mcp-testingSkill
- tauri-mcp-test-runnerSkill
- tauri-v2-integrationSkill
- tiptap-devSkill
- tiptap-editorSkill
- translate-docsSkill
- workflow-auditSkill
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.

