/mcp-check
Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check.
$ npx -y skills add claude-world/director-mode-lite --skill mcp-check --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
- Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.
- You can call itInvoke it directly when you want it.
- Slash command
/mcp-check
Context preview
The summary Claude sees to decide when to auto-load this skill.
Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check.
SKILL.md
mcp-check.SKILL.mdname: mcp-check
description: Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check.
user-invocable: true
MCP Configuration Validator
Validate the project's MCP setup for correctness and completeness.
---
Validation Steps
1. Check Configuration Files
| File | Scope | What lives here | |------|-------|-----------------| | `.mcp.json` (project root) | Project | `mcpServers` — the server definitions, written by `claude mcp add --scope project` | | `.claude/settings.json` | Project | Toggles only: `enableAllProjectMcpServers`, `enabledMcpjsonServers` | | `~/.claude.json` | User | User-scope `mcpServers`, available across all projects |
**The source of truth for project servers is `.mcp.json` at the project root.** Read `mcpServers` from there — `.claude/settings.json` never holds server definitions, only approval toggles.
2. Validate Structure
- [ ] `.mcp.json` is valid JSON (no trailing commas)
- [ ] `mcpServers` object exists in `.mcp.json`
- [ ] Project servers are approved via `.claude/settings.json`: either `enableAllProjectMcpServers: true`, or each server named in `enabledMcpjsonServers`
3. Validate Each MCP
- [ ] `command` is valid
- [ ] `args` properly formatted
- [ ] `env` variables set
4. Check Essential MCPs
| MCP | Required? | |-----|-----------| | memory | Recommended | | filesystem | Optional | | github | If .git exists |
5. Security Check
- [ ] No hardcoded secrets
- [ ] Sensitive values use env vars
---
Output Format
## MCP Configuration Report
### Status: VALID / ISSUES / INVALID
### Configuration Summary
| MCP Server | Status | Notes |
|------------|--------|-------|
| memory | OK/FAIL | details |
### Issues Found
1. [Issue and fix]
### Missing Recommended MCPs
- memory: `claude mcp add --scope project memory...`
---
Common Issues
| Issue | Fix | |-------|-----| | Invalid JSON | Check trailing commas | | MCP not loading | `claude mcp reset-project-choices` | | Missing env vars | Add with `-e KEY=value` |
Read more
name: mcp-check description: Validate MCP configuration and suggest improvements. Use when MCP servers fail to load, after editing .mcp.json, or when the user runs /mcp-check. user-invocable: true
MCP Configuration Validator
Validate the project's MCP setup for correctness and completeness.
---
Validation Steps
1. Check Configuration Files
| File | Scope | What lives here | |------|-------|-----------------| | `.mcp.json` (project root) | Project | `mcpServers` — the server definitions, written by `claude mcp add --scope project` | | `.claude/settings.json` | Project | Toggles only: `enableAllProjectMcpServers`, `enabledMcpjsonServers` | | `~/.claude.json` | User | User-scope `mcpServers`, available across all projects |
**The source of truth for project servers is `.mcp.json` at the project root.** Read `mcpServers` from there — `.claude/settings.json` never holds server definitions, only approval toggles.
2. Validate Structure
- [ ] `.mcp.json` is valid JSON (no trailing commas)
- [ ] `mcpServers` object exists in `.mcp.json`
- [ ] Project servers are approved via `.claude/settings.json`: either `enableAllProjectMcpServers: true`, or each server named in `enabledMcpjsonServers`
3. Validate Each MCP
- [ ] `command` is valid
- [ ] `args` properly formatted
- [ ] `env` variables set
4. Check Essential MCPs
| MCP | Required? | |-----|-----------| | memory | Recommended | | filesystem | Optional | | github | If .git exists |
5. Security Check
- [ ] No hardcoded secrets
- [ ] Sensitive values use env vars
---
Output Format
## MCP Configuration Report ### Status: VALID / ISSUES / INVALID ### Configuration Summary | MCP Server | Status | Notes | |------------|--------|-------| | memory | OK/FAIL | details | ### Issues Found 1. [Issue and fix] ### Missing Recommended MCPs - memory: `claude mcp add --scope project memory...`
---
Common Issues
| Issue | Fix | |-------|-----| | Invalid JSON | Check trailing commas | | MCP not loading | `claude mcp reset-project-choices` | | Missing env vars | Add with `-e KEY=value` |
Use Claude Code like a Director, not a Programmer. MIT toolkit with Auto-Loop, guided setup, 27 commands, 14 agents, and 32 skills.
Other skills on director-mode-lite.
- /changelog-observer
Track development session events in a daily markdown changelog, including file changes, test results, and key decisions.
Open skill - /agent-check
Validate custom agent file format and structure. Use after creating or editing an agent, before committing agent changes, or when an agent fails to load.
Open skill - /agent-template
Generate custom agent from template. Use when creating a new subagent from scratch, or scaffolding an agent file with correct frontmatter.
Open skill - /agents
List all available agents (core, expert, self-evolving). Use when the user asks what agents are available or runs /agents.
Open skill - /auto-loop
TDD-based autonomous development loop with checkpoint recovery and observability changelog
Open skill - /changelog
View and manage the runtime changelog for observability
Open skill

