What does mcp-check validate?

It validates MCP configuration in both project and user settings, including JSON structure, required fields like mcpServers and enableAllProjectMcpServers, per-MCP command/args/env, and security checks.

How should I interpret the Status values?

VALID means the MCP config passes all checks; ISSUES indicates non-critical problems that should be addressed; INVALID signals major problems (e.g., invalid JSON) that must be fixed before use.

How do I fix issues reported by mcp-check?

Follow the report's recommendations: correct JSON formatting, ensure required fields exist, configure or add missing MCPs, and set env vars instead of hardcoding secrets. Re-run until the Status reports as VALID.

mcp-check

npx machina-cli add skill claude-world/director-mode-lite/mcp-check --openclaw

Files (1)

SKILL.md

1.3 KB

MCP Configuration Validator

Validate the project's MCP setup for correctness and completeness.

Validation Steps

1. Check Configuration Files

.claude/settings.json (project)
~/.claude.json (user, reference)

2. Validate Structure

Valid JSON format
mcpServers object exists
enableAllProjectMcpServers: true is set

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`

Source

git clone https://github.com/claude-world/director-mode-lite/blob/main/skills/mcp-check/SKILL.mdView on GitHub

Overview

MCP Configuration Validator checks your project (.claude/settings.json) and user (~/.claude.json) MCP settings for correctness and completeness. It verifies JSON structure, required fields, essential MCPs, and security checks, and outputs a Markdown report with fixes.

How This Skill Works

It loads the project and user MCP configs, validates JSON syntax, checks for an mcpServers object and enableAllProjectMcpServers: true, and validates each MCP's command, args, and env settings. It then emits an MCP Configuration Report, highlighting status (VALID/ISSUES/INVALID) and recommended fixes.

When to Use It

Setting up MCP for the first time in a project
Auditing an existing MCP configuration for completeness
Troubleshooting MCP not loading or missing settings
Verifying security by ensuring no hardcoded secrets
Ensuring essential MCPs (e.g., memory) are present

Quick Start

Step 1: Run claude mcp-check in the project root to validate MCP config
Step 2: Review the generated MCP Configuration Report for Status, Summary, and Issues
Step 3: Apply fixes (e.g., fix JSON syntax, ensure mcpServers, add or configure memory) and re-run until Status is VALID

Best Practices

Validate JSON syntax before running checks
Ensure .claude/settings.json and ~/.claude.json are correct
Check each MCP's command, args, and env thoroughly
Avoid hardcoded secrets; prefer environment variables
Run the validator after changes and re-check until Status is VALID

Example Use Cases

Report shows Status: VALID after fixes
Missing enableAllProjectMcpServers flagged in report
Invalid JSON detected due to trailing comma
Missing env vars for a memory MCP
Github MCP considered only if a .git directory exists

Frequently Asked Questions

Add this skill to your agents