SkillAgentSearch skills...

disable-claude-mcp

🔧 A workaround for selectively disabling mcpServers in Claude Desktop using YAML + yq. Define your config in YAML, mark servers as enabled: false, and generate a clean JSON config automatically.

Install / Use

claude mcp add zudochkin -- npx -y github:zudochkin/disable-claude-mcp

If the server publishes to npm under a different name, use that package instead — check the repo README.

About this skill
🔌

MCP Server

Model Context Protocol server

Quality Score

62/100

Category

Automation

Supported Platforms

Claude Code
Claude Desktop

Tags

Our assessment of disable-claude-mcp

disable-claude-mcp scores 62/100 on our quality scale, 2704th of 2,857 Automation skills we index.

Its MCP Server is 2.3 KB long, well organised into 9 sections with 5 code examples: moderately detailed.

It has 3 GitHub stars, so there is little community track record yet; judge it on its content.

Substance
20/30
Structure
20/20
Description
15/15
Adoption
3/20
Freshness
5/15

Maintenance, license and trust

  • The repository was last updated about 16 months ago. Expect some instructions to reference tool versions or APIs that have since changed.
  • Our last check on 2026-09-14 found the source still online.
  • No license is declared. By default that means all rights are reserved: you can read it, but reusing or redistributing it is not clearly permitted. Ask the author before building on it commercially.
  • Its trust signals score 68/100, with 3 cautions from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.

AI review by kimi-k2.7-code on 2026-11-01. Automated pattern scan on 2026-11-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

disable-claude-mcp compared with similar skills

All 4 of these similar skills score higher than disable-claude-mcp; compare them before choosing.

SkillScoreStarsUpdatedFormat
disable-claude-mcp (this skill)by zudochkin62316mo agoMCP Server
Agent-Reachby Panniantong100107.3k7d agoCLAUDE.md
headroomby headroomlabs-ai10078.5k1d agoCLAUDE.md
CowAgentby zhayujie10047.7ktodayCLAUDE.md
Scraplingby D4Vinci10091.2ktodayMCP Server

Frequently asked questions

How do I install disable-claude-mcp?
Run claude mcp add zudochkin -- npx -y github:zudochkin/disable-claude-mcp. The install tabs above show the steps for each supported agent.
Which AI agents does disable-claude-mcp work with?
It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
Is disable-claude-mcp safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It declares no license and scores 68/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is disable-claude-mcp still maintained?
The repository was last updated about 16 months ago. Expect some instructions to reference tool versions or APIs that have since changed.

🛠 Disable MCP Servers in Claude Desktop (via YAML + yq)

Claude Desktop does not natively support disabling individual mcpServers via claude_desktop_config.json using flags like enabled: false.

This guide shows a clean and reliable workaround: define your configuration in YAML (where you can mark servers as disabled), and convert it to JSON while filtering out those marked as disabled — using yq.


📦 Prerequisites


🧭 Steps

0. (Optional) Convert existing JSON config to YAML

If you already have a claude_desktop_config.json file and want to migrate to this new workflow:

yq "claude_desktop_config.json" -o=yaml > claude_config.yaml

You can now edit claude_config.yaml freely.


1. Backup your current JSON config

mv claude_desktop_config.json claude_desktop_config.backup.json

2. Create or edit claude_config.yaml

This YAML file allows you to temporarily disable MCP servers via enabled: false:

globalShortcut: ""
mcpServers:
  my-server-1:
    enabled: false
    command: some-command
    args:
      - arg1
      - arg2
  my-server-2:
    command: another-command
    args:
      - --flag
      - value
    env:
      SOME_ENV_VAR: /path/to/data

You can define as many servers as needed. Only those without enabled: false will be kept.


3. Convert YAML to cleaned JSON (skipping disabled servers)

Run this command:

yq -o=json '.mcpServers |= with_entries(select(.value.enabled != false))' claude_config.yaml > claude_desktop_config.json

This will:

  • Remove any mcpServers that are marked enabled: false
  • Output valid JSON Claude Desktop can use

✅ Result Example (claude_desktop_config.json)

{
  "globalShortcut": "",
  "mcpServers": {
    "my-server-2": {
      "command": "another-command",
      "args": [
        "--flag",
        "value"
      ],
      "env": {
        "SOME_ENV_VAR": "/path/to/data"
      }
    }
  }
}

💡 Why this works

Claude Desktop doesn't process enabled: false — but by removing those entries entirely before export, it never sees them.

This gives you a toggle-able YAML workspace with selective activation, while keeping the final JSON clean and compatible.

Related Skills

View on GitHub
GitHub Stars3
CategoryAutomation
Updated1y ago
Forks0

Trust signals

68/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

2 medium1 low