Just like npm installs the right packages, Mother MCP installs the right AI skills for your stack. No manual config. No context switching. Just setup and code.
/plugin marketplace add dmgrok/mcp_mother_skills
/plugin install mother-mcp@mother-mcp-marketplace
npm install -g mcp-mother-skills
"If you'll do roughly the same thing 10+ times, encode it as a skill. Under 3 times? Just prompt."
Hey Claude, review this PR for security issues. Check for SQL injection, XSS, also we use React so watch for dangerouslySetInnerHTML, and our team prefers early returns, and don't forget we have a custom auth middleware pattern, and...
Re-typed variations. Inconsistent results. Teammates can't find "that good prompt you used."
/review
Skill knows your framework, patterns, and team standards — installed from your actual project context.
Re-typing similar prompts wastes hours weekly
Skills encode best practices once, reuse forever
Small phrasing changes alter AI behavior
Versioned skills deliver predictable results
"What was that prompt you used last month?"
Named skills with descriptions, searchable
Everyone crafts prompts differently
Shared skills encode house style
Real problems developers face every day with AI assistants.
Jumping between React, Python, and Rust projects? Your AI forgets everything between sessions.
Mother detects your stack and loads the right skills. Every. Single. Time.
New teammate spends 2 hours configuring AI skills. Then does it wrong anyway.
Clone repo → sync_skills → Done. Perfect AI context in 5 seconds.
Editing .github/skills/ manually across 10 microservices. Skills get stale. Nobody updates them.
Skills update when your dependencies change. Always current. Zero maintenance.
Want to try Copilot but your team uses Claude? Reconfigure everything from scratch.
Switch between Claude, Copilot, and Codex. Context follows you automatically.
See what you're missing.
sync_skills
Real scenarios where Mother saves you hours.
The Problem: Frontend in React, backend in Python, infra in Terraform. Your AI is confused.
Mother's Solution: Detects all languages, loads relevant skills for each. Your AI becomes a polyglot too.
The Problem: Different packages need different skills. Manual config nightmare across 20+ packages.
Mother's Solution: Per-package skill detection. Each service gets exactly what it needs, automatically.
The Problem: API service needs different skills than frontend. Skills leak between services.
Mother's Solution: Context-aware per-service skills. No cross-contamination. Perfect isolation.
The Problem: Clone repo → spend 20 minutes configuring AI → finally start contributing.
Mother's Solution: Clone → sync_skills → contribute. Zero friction from discovery to first PR.
The Problem: Moving from Webpack to Vite? Your AI still suggests Webpack configs.
Mother's Solution: Detects new dependencies, updates skills automatically. AI adapts as you migrate.
The Problem: Everyone has different AI skills. Inconsistent code patterns across the team.
Mother's Solution: Shared config means everyone gets the same skills. Consistent patterns, always.
One server, all your favorite AI coding assistants.
Full support with auto-detection via environment variables and MCP client info.
Seamless VS Code integration. Skills installed to .github/skills automatically.
Follows the Open Agent Skills Standard. Compatible with AGENTS.md workflow.
Skills optimized for v0's AI-powered frontend generation and deployment workflow.
| Priority | Method | Example |
|---|---|---|
| 1 | Config Override | agent.force: claude |
| 2 | Environment Variables | CLAUDE_CODE=1, GITHUB_COPILOT, CODEX_HOME |
| 3 | MCP Client Info | Client name contains "claude", "copilot", or "codex" |
| 4 | Project Structure | .claude/, .github/copilot-instructions.md, AGENTS.md |
| 5 | Home Directory | ~/.claude/skills/, ~/.copilot/skills/ |
From detection to installation in seconds.
Mother uses a 3-tier detection strategy for comprehensive tech stack analysis.
GitHub SBOM
→ 340+ packages from dependency graph
Specfy Analyser
→ 700+ technologies, infrastructure, SaaS
Local Scanning
→ package.json, requirements.txt, configs
Git Remote
→ Auto-detects GitHub repo from .git/config
Compares detected technologies against the skill registry to find relevant skills.
Downloads skills to the appropriate directory for your AI agent.
.claude/skills/
.github/skills/
.codex/skills/
3-tier strategy for comprehensive tech stack analysis.
Most Accurate — Fetches the Software Bill of Materials directly from GitHub's dependency graph.
GITHUB_TOKEN=ghp_xxx sync_skills
Most Comprehensive — Detects 700+ technologies including infrastructure and SaaS.
Works offline with local analysis
Always Available — Traditional file scanning for offline environments.
No external dependencies
Mother automatically detects your GitHub repository from local git configuration:
git@github.com:owner/repo.git
https://github.com/owner/repo.git
ssh://git@github.com/owner/repo
Curated from Anthropic, OpenAI, GitHub, and the community.
Skills are fetched from the Agent Skills Directory, an automatically updated catalog.
Curated from the best AI agent skill repositories.
Official Claude skills for documents, design, and enterprise workflows
16 skillsOfficial skills following the Open Agent Skills Standard
12 skillsGitHub workflow skills for CI/CD, PR reviews, and automation
26 skillsAggregated catalog from 6 providers (Anthropic, GitHub, OpenAI, HuggingFace, Vercel, SkillCreator.ai)
112 skillsWant skills tailored for your organization? The registry URL is fully configurable:
# .mcp/mother/config.yaml
registry:
# Use your company's private registry
- url: "https://skills.yourcompany.com/catalog.json"
priority: 1
# Optionally keep the public registry as fallback
- url: "https://cdn.jsdelivr.net/gh/dmgrok/agent_skills_directory@main/catalog.json"
priority: 2Let Mother detect skills automatically, or take full control.
Mother scans your project and installs matching skills automatically.
package.json
sync_skills
Run at start of each session
package.json — npm dependenciesrequirements.txt — Python packagespyproject.toml — Python projectsCargo.toml — Rust cratesgo.mod — Go modules*.config.js — Framework configsDockerfile — Docker projectsREADME.md — Keyword extractionSearch and install specific skills by name when you need them.
search_skills "design"
install_skill "canvas-design"
search_skills "query"
Find skills by name or keyword
install_skill "name"
Install a specific skill
uninstall_skill "name"
Remove an installed skill
Configure in .mcp/mother/config.yaml:
skills:
always_include:
- mcp-builder
- skill-creator
always_exclude:
- deprecated-skillCurated collections of skills for common development workflows. Install a complete stack with one command.
Instead of installing skills one by one, get everything you need for React, Next.js, or MCP development in seconds.
Bundles are curated from the Agent Skills Directory — real skills that work together.
Find bundles by what you want to build: "SaaS", "mobile app", "AI assistant", or browse by category.
Modern React development with testing and best practices
Complete Next.js stack with deployment
Build Model Context Protocol servers
Machine learning with HuggingFace
Create PDFs, DOCX, PPTX, and spreadsheets
GitHub CLI, Actions, and CI/CD workflows
list_bundlesSee all available bundles with descriptions
list_bundles query="react"Filter by name, description, or use case
install_bundle "frontend-react"Install all skills in the bundle at once
18 curated bundles across 8 categories. View all bundles →
Get Mother MCP running in under 5 minutes.
Easiest way to get started in Claude Code:
/plugin marketplace add dmgrok/mcp_mother_skills
/plugin install mother-mcp@mother-mcp-marketplaceFor manual configuration or other agents:
# Install globally
npm install -g mcp-mother-skills
# Or use with npx (no install needed)
npx mcp-mother-skillsFor development or custom modifications:
git clone https://github.com/dmgrok/mcp_mother_skills.git
cd mcp_mother_skills
npm install
npm run buildAdd to your project's .mcp.json:
{
"mcpServers": {
"mother-skills": {
"command": "npx",
"args": ["mcp-mother-skills"],
"env": {
"MOTHER_PROJECT_PATH": "."
}
}
}
}{
"mcpServers": {
"mother-skills": {
"command": "node",
"args": ["/path/to/mcp_mother_skills/dist/index.js"],
"env": {
"MOTHER_PROJECT_PATH": "."
}
}
}
}Add to your .vscode/mcp.json:
{
"mcp.servers": {
"mother-skills": {
"command": "npx",
"args": ["mcp-mother-skills"],
"env": {
"MOTHER_PROJECT_PATH": "${workspaceFolder}"
}
}
}
}{
"mcp.servers": {
"mother-skills": {
"command": "node",
"args": ["${workspaceFolder}/path/to/mcp_mother_skills/dist/index.js"],
"env": {
"MOTHER_PROJECT_PATH": "${workspaceFolder}"
}
}
}
}Add to ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"mother-skills": {
"command": "npx",
"args": ["mcp-mother-skills"],
"env": {
"MOTHER_PROJECT_PATH": "/path/to/your/project"
}
}
}
}{
"mcpServers": {
"mother-skills": {
"command": "node",
"args": ["/path/to/mcp_mother_skills/dist/index.js"],
"env": {
"MOTHER_PROJECT_PATH": "/path/to/your/project"
}
}
}
}Add to your project's .v0/mcp.json:
{
"mcpServers": {
"mother-skills": {
"command": "npx",
"args": ["mcp-mother-skills"],
"env": {
"MOTHER_PROJECT_PATH": "."
}
}
}
}{
"mcpServers": {
"mother-skills": {
"command": "node",
"args": ["/path/to/mcp_mother_skills/dist/index.js"],
"env": {
"MOTHER_PROJECT_PATH": "."
}
}
}
}Add these instructions to your project so Mother MCP auto-initializes at the start of each session.
Add to .github/copilot-instructions.md:
## Startup
At the start of each conversation, call `setup` (for first-time use)
or `sync_skills` (for ongoing updates) to ensure project-relevant
skills are loaded.Add to CLAUDE.md in your project root:
## Startup
At the start of each conversation, call `setup` (for first-time use)
or `sync_skills` (for ongoing updates) to ensure project-relevant
skills are loaded.Add to AGENTS.md in your project root:
## Startup
At the start of each conversation, call `setup` (for first-time use)
or `sync_skills` (for ongoing updates) to ensure project-relevant
skills are loaded.Add to .cursorrules in your project root:
## Startup
At the start of each conversation, call `setup` (for first-time use)
or `sync_skills` (for ongoing updates) to ensure project-relevant
skills are loaded.Add to .v0/instructions.md in your project root:
## Startup
At the start of each conversation, call `setup` (for first-time use)
or `sync_skills` (for ongoing updates) to ensure project-relevant
skills are loaded.Start a conversation and say:
Setup my Mother MCPThat's it! Mother will detect your project, show recommendations, and let you install matching skills.
Everything you need to manage skills.
setup
Start here! Initialize Mother MCP, scan your project, and get skill recommendations.
sync_skills
Synchronize skills based on detected technologies. Run this to keep skills up to date.
get_project_context
View detected stack and installed skills.
get_agent_info
See which AI agent is detected.
search_skills
Search for available skills by name or keyword.
list_bundles
NEW! Browse curated skill bundles by category or use case.
install_bundle
NEW! Install a complete skill bundle at once.
install_skill
Manually install a specific skill.
uninstall_skill
Remove an installed skill.
check_updates
Check for skill updates.
redetect
Re-scan project files.
reset_skills
Start fresh - Remove all installed skills and optionally clear config.
Join developers who've automated their AI skills and reclaimed hours every week.
Building the npm for AI skills — together.
Coming soon: Skill ratings, download counts, verified publishers, and reviews from the community.
Publish your skills to the registry with a simple CLI command. Templates and guides included.
mother publish CLIJoin us in building the best AI skills ecosystem. Every contribution matters.