mcp-setup
Skill0 starsChanged 27 days agoMITView on GitHub
Self-install MCP servers to expand Claude's capabilities. Read the catalog, install the server, wire it into .mcp.json, and test.
- Reads credentials
- Installs packages
17 other projects use a version of this, 2 of them edited.
Adopted by
Most recently taken up by
- naman10parikh/pennyword for word, first seen Nov 8, 2026
- naman10parikh/wikimemedited, first seen Nov 8, 2026
- DebugSwift/XcodeBazelMCPtheir own version, first seen Nov 1, 2026
- naman10parikh/turboword for word, first seen Oct 25, 2026
- jonmumm/skillstheir own version, first seen Oct 21, 2026
- naman10parikh/agentgridedited, first seen Oct 20, 2026
Other versions17 projects use a version of this.
Word for word · 2
- naman10parikh/penny★ 0100% same
- naman10parikh/turbo★ 0100% same
Edited · 2
- naman10parikh/agentgrid★ 999% same
- naman10parikh/wikimem★ 899% same
Wrote their own version · 13
- thejaustin/ShizukuPlus★ 1.7ksame name
- vellum-ai/vellum-assistant★ 1.5ksame name
- babamba2/superclaude-for-sap★ 73same name
- DebugSwift/XcodeBazelMCP★ 9same name
- ingpoc/SKILLS★ 9same name
- mintorain/mintorain-tmux-ocastra★ 8same name
- hajekim/agentic-design-patterns-skills★ 4same name
- AzamatRaimbekov/vibe-coding-mentor★ 3same name
- jonmumm/skills★ 2same name
- hajekim/agentic-design-patterns-extension★ 1same name
3 more not listed
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 repository59 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms.txtllms.txt
- agent-runtimeSkill
- frontend-designSkill
- architectSkill
- deep-thinkSkill
- design-systemsSkill
- ecosystem-referenceSkill
- fractal-delegationSkill
- harness-reviewSkill
- heartbeatSkill
- integrate-resourcesSkill
- llm-council-critiqueSkill
- loop-createSkill
- memory-compressionSkill
- memorySkill
- model-routingSkill
- oss-project-scaffoldSkill
- playwright-cliSkill
- repo-scoutSkill
- self-improveSkill
- skill-creatorSkill
- skill-routingSkill
- sprintSkill
- test-visualSkill
- troubleshootSkill
- ux-auditSkill
- Accessibility AuditorSkill
- artifacts-builderSkill
- brand-guidelinesSkill
- canvas-designSkill
- frontend-patternsSkill
- design-mirrorSkill
- design-system-starterSkill
- design-to-codeSkill
- feature-design-assistantSkill
- figma-implement-designSkill
- frontend-designSkill
- frontend-dev-guidelinesSkill
- mobile-designSkill
- motion-canvasSkill
- pixel-agent-uiSkill
- pixel-animateSkill
- pixel-anti-slopSkill
- pixel-brain-pageSkill
- pixel-migrate-next16Skill
- pixel-rsc-boundarySkill
- pixel-ship-gateSkill
- premium-web-designSkill
- senior-frontendSkill
- shadcnSkill
- tailwind-design-systemSkill
- tailwind-patternsSkill
- theme-factorySkill
- ui-design-systemSkill
- ui-ux-pro-maxSkill
- ux-researcher-designerSkill
- web-design-guidelinesSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 12 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
Check these sources in order:
- Very specific: line 97
Read the current .mcp.json:
- Distinctive: line 103
Add the new server entry. Preserve all existing entries.
- Distinctive: line 108
Test by invoking one of the server's tools
- Very specific: line 109
If it fails: check logs, verify env vars, try npx directly
- Very specific: line 113
Add the new server to resources/awesome-repos.md under a "Currently Installed" section.
- Very specific: line 129
NEVER install servers that require sudo or root access
- Distinctive: line 130
NEVER pass secrets directly in args — use env vars
- Distinctive: line 131
NEVER install from untrusted sources (verify GitHub stars, maintainer)
- Distinctive: line 132
Always test in isolation before wiring into the main config
“Common” is measured: kept by at least 6 in 10 of the 12 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
When to Use
- User says "install the [X] MCP server" or "set up [X] MCP"
- You need a capability that an MCP server provides (database access, API, browser, etc.)
- During resource integration when an article mentions a useful MCP server
Process
1. Find the Server
Check these sources in order:
resources/awesome-repos.md(our local catalog)- https://github.com/punkpeye/awesome-mcp-servers (82K+ stars, 2,500+ servers)
- npm registry:
npm search mcp-server-[name] - GitHub search:
mcp server [name]
2. Evaluate Before Installing
- Does it duplicate an existing capability? (Check current .mcp.json first)
- Is it actively maintained? (Last commit < 3 months ago)
- Does it have security concerns? (Never install servers that require write access to system files)
- Is it worth the token overhead? (~4,200 tokens per MCP server vs ~70 for a skill)
Rule: If a skill can do the job, prefer the skill. MCPs are for external integrations only.
3. Install
For npx-based servers (most common):
# Test it works first
npx -y @modelcontextprotocol/server-[name] --helpThen update .mcp.json:
{
"mcpServers": {
"[name]": {
"command": "npx",
"args": ["-y", "@modelcontextprotocol/server-[name]"],
"env": {}
}
}
}For pip-based servers:
pip install mcp-server-[name]Then update .mcp.json:
{
"mcpServers": {
"[name]": {
"command": "python",
"args": ["-m", "mcp_server_[name]"],
"env": {}
}
}
}For Docker-based servers:
docker pull mcp/[name]Then update .mcp.json:
{
"mcpServers": {
"[name]": {
"command": "docker",
"args": ["run", "-i", "--rm", "mcp/[name]"],
"env": {}
}
}
}4. Wire Into Settings
Read the current .mcp.json:
cat ~/energy/.mcp.jsonAdd the new server entry. Preserve all existing entries.
5. Verify
- Restart Claude Code session (or the server auto-discovers on next tool call)
- Test by invoking one of the server's tools
- If it fails: check logs, verify env vars, try
npxdirectly
6. Document
Add the new server to resources/awesome-repos.md under a "Currently Installed" section.
Common MCP Servers Worth Having
| Server | What It Does | Install |
| filesystem | Read/write files with permissions | npx -y @modelcontextprotocol/server-filesystem |
| github | GitHub API (PRs, issues, repos) | npx -y @modelcontextprotocol/server-github |
| postgres | Query PostgreSQL databases | npx -y @modelcontextprotocol/server-postgres |
| fetch | HTTP requests with smart rendering | npx -y @modelcontextprotocol/server-fetch |
| memory | Key-value persistent memory | npx -y @modelcontextprotocol/server-memory |
| puppeteer | Browser automation | npx -y @modelcontextprotocol/server-puppeteer |
| firecrawl | Web scraping and crawling | npx -y firecrawl-mcp (requires FIRECRAWL_API_KEY) |
Security Rules
- NEVER install servers that require
sudoor root access - NEVER pass secrets directly in args — use env vars
- NEVER install from untrusted sources (verify GitHub stars, maintainer)
- Always test in isolation before wiring into the main config
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

