Summary
If you've ever wondered why MCPs are loading in every Claude Code session and eating your context budget, this is your fix. The key insight: never put MCP servers in the global mcpServers section of ~/.claude.json. Instead, use project-level .mcp.json files so MCPs only load when you're actually working in that project. The skill walks through checking all three config locations (user config, project config, settings.json), moving servers to the right place, and cleaning up permission overrides that can silently re-enable things. It's essentially a field guide to the MCP config priority system, with ready-to-run Python snippets for each cleanup task.
Install to Claude Code
npx -y skills add libukai/awesome-agent-skills --skill mcp-config --agent claude-codeInstalls into .claude/skills of the current project.
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →
An agent that runs the SEO playbooks that move rankings and ships PRs you control.
Get founding access →
Connect Claude to +800M contacts, +150M companies. Find & Enrich leads in chat.
Try For Free →Files
SKILL.md
Select a file.
Featured
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →On Capafy, your Skill runs online 24/7 as an agent product, and you get paid every time someone uses it.
Start earning →An agent that runs the SEO playbooks that move rankings and ships PRs you control.
Get founding access →Connect Claude to +800M contacts, +150M companies. Find & Enrich leads in chat.
Try For Free →
