mcp-check

Audit MCP server and plugin configurations across workspace files for schema and syntax errors.

1|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/s0lci700/OVERLAYS --skill mcp-check-s0lci700
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: mcp-check
Source: https://github.com/s0lci700/OVERLAYS/tree/main/.claude/skills/mcp-check
Command: npx skills add https://github.com/s0lci700/OVERLAYS --skill mcp-check-s0lci700

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Audit all MCP server and plugin configurations across workspace files to surface duplicates, misplaced entries, JSON errors, and schema issues, and offer optional fixes.

Core Features & Use Cases

  • Inventory and audit MCP config across project- and user-level locations
  • Detect wrong file placement, duplicates, JSON syntax errors, and schema issues
  • Optional safe fixes that deduplicate, relocate entries, and correct structure

Quick Start

Run the mcp-check command in your workspace to audit MCP config files and, with --fix, apply safe fixes.

Frequently Asked Questions about mcp-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit MCP server configs for duplicates and schema errors?

To audit MCP server configs, run the mcp-check command in your workspace to inventory all project- and user-level entries, surfacing duplicates, misplaced files, JSON syntax errors, and missing schema fields automatically.

What causes a broken MCP config setup in Claude?

Broken MCP setups stem from misplaced configuration entries, duplicated servers across files, JSON syntax errors, or invalid mcpServer schemas missing required fields like command, url, args, or env variables.

Can I automatically fix and deduplicate MCP config entries?

Yes, you can automatically deduplicate and fix MCP config entries by running the audit command with the --fix flag, which safely relocates misplaced entries and corrects structural issues across workspace files.

Which files are checked during an MCP config audit?

An MCP config audit checks project-level paths like .mcp.json, .claude/settings.json, .claude/settings.local.json, alongside user-level configuration locations to unify all entries into a single inventory report.

Why is my MCP server not loading despite being in settings.json?

Your MCP server may not load if the settings.json entry has schema violations, such as missing required command or url fields, or if the configuration is misplaced outside expected project or user-level paths.