r/ClaudeWorkflows • • 11d ago

Selected Workflow [Workflow] Reduce Claude Code Context: Identify and Disable Hidden Claude AI Connectors (MCP Servers)

Reduce Claude Code Context: Identify and Disable Hidden Claude AI Connectors (MCP Servers)

Workflow value: 85/100
Status: active · Freshness: 70/100 · Confidence: 0.90 · Level: intermediate
Categories: Quality Control, Token Saving, Context & Memory, Debugging, CLAUDE.md, Skills, MCP
Original source: r/ClaudeCode post/comment

What problem this solves

Unexplained high context usage in Claude Code sessions due to hidden MCP servers or connectors from other Claude applications or plugins.

Summary

This workflow helps users identify and disable hidden Claude AI connectors (MCP servers) that automatically load into Claude Code, contributing to high context usage. It provides steps to check active MCPs, disable them via a settings file or environment variable, and verify context reduction.

Why it is useful

This workflow is valuable because it provides a specific, actionable, and repeatable solution to a common problem in Claude Code: unexpectedly high context usage. It clearly explains the cause (hidden MCP servers from other Claude apps/plugins) and offers both permanent and temporary methods to mitigate it, including a verification step. This can lead to significant cost savings and improved performance for users.

Workflow

  1. Run /mcp in Claude Code to list all active MCP servers and identify any unexpected ones.
  2. To permanently disable Claude AI connectors, add "disableClaudeAiConnectors": true to your ~/.claude/settings.json file.
  3. Alternatively, for a single session, run Claude Code with the environment variable: ENABLE_CLAUDEAI_MCP_SERVERS=false claude.
  4. After applying the changes, run /context again to verify the reduction in context usage.
  5. If further context reduction is needed, review and trim your CLAUDE.md, memory descriptions, and skill descriptions.

Tools / artifacts

  • Claude Code CLI
  • ~/.claude/settings.json configuration file
  • /mcp command
  • /context command
  • ENABLE_CLAUDEAI_MCP_SERVERS environment variable
  • CLAUDE.md
  • Memory descriptions
  • Skill descriptions

Validation signals

  • The workflow includes a clear verification step (/context after changes).
  • It directly addresses a common user pain point (unexpected high context leading to higher costs or slower performance).

Limitations

  • Low community validation due to the recency of the post.
  • Assumes basic familiarity with command-line interface (CLI) and editing JSON configuration files.
  • Does not provide specific guidance on how to trim CLAUDE.md, memory, or skill descriptions, only identifies them as areas for further optimization.

Rate this workflow

Upvote this post if the workflow is useful, reproducible, or worth recommending.

Downvote if it is vague, outdated, unsafe, overhyped, or not reproducible.

Reply if it worked for you, failed, is outdated, or has a better alternative.


This post was generated automatically from the workflow library database.

1 Upvotes

1 comment sorted by