Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
A direct command skips the review prompt. Inspect the source before running it.
Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.
This skill is an orchestration hub, not a CLI. It activates
inside a Claude Code session when one of the trigger keywords
below appears, or when invoked explicitly:
Skill(conserve:mcp-code-execution)
The hub then routes to the relevant sub-skill modules
(mcp-subagents, mcp-patterns, mcp-validation) based on
the detected workflow shape. There is no separate install
step or CLI entry point.
When To Use
Automatic: Keywords: code execution, MCP, tool chain, data pipeline, MECW
Tool Chains: >3 tools chained sequentially
Data Processing: Large datasets (>10k rows) or files (>50KB)
Context Pressure: Current usage >25% of total window (proactive context management)
MCP Tool Search (Claude Code 2.1.7+): When MCP tool
descriptions exceed 10% of context, tools are automatically
deferred and discovered via MCPSearch instead of being loaded
upfront. This reduces token overhead by ~85% but means tools
must be discovered on-demand. Haiku models do not support tool
search. Configure threshold with ENABLE_TOOL_SEARCH=auto:N
where N is the percentage.
Subagent MCP Access Fix (Claude Code 2.1.30+): SDK-provided
MCP tools are now properly synced to subagents. Prior to 2.1.30,
subagents could not access SDK-provided MCP tools: workflows
delegating MCP tool usage to subagents were silently broken. No
workarounds needed on 2.1.30+.
Claude.ai MCP Connectors (Claude Code 2.1.46+): Users logged
into Claude Code with a claude.ai account may have additional
MCP tools auto-loaded from claude.ai/settings/connectors. These
tools contribute to the tool search threshold count. If
workflows unexpectedly trigger tool search or context inflation,
check /mcp for claude.ai-sourced connectors. Known reliability
issue: connectors can silently disappear (GitHub #21817).
MCP Prompt Cache Fix (Claude Code 2.1.70+): MCP servers with
instructions connecting after the first turn no longer bust the
prompt cache. Previously, a late-connecting MCP server would
invalidate cached prompt prefixes, increasing token costs for
the rest of the session. On 2.1.70+, prompt cache reuse is
preserved regardless of when MCP servers connect.
ToolSearch Reliability Fix (Claude Code 2.1.70+): Empty
model responses after ToolSearch are fixed. The server was
rendering tool schemas with system-prompt-style tags that could
confuse models into stopping early. ToolSearch-heavy workflows
(many deferred MCP tools) are now more reliable.
MECW Compliance: 100% adherence to 50% context rule
Token Efficiency: Maintain >80% savings vs traditional methods
Module Coordination: <5% overhead for hub orchestration
Exit Criteria
Workflow classified into one of the three MECW strategies
(aggressive/moderate/conservative) with the correct module
roster (mcp-subagents, mcp-patterns, mcp-validation)
selected based on tool-chain length and data size
Context usage remains at or below 50% of the total window
throughout the workflow; any breach triggers the hub-level
emergency response (delegate to mcp-validation, route to
mcp-subagents, apply compression)
synthesize_module_results returns a dict with all four
keys: status, token_savings, mecw_compliance,
hallucination_risk
Token savings reported at the end of the workflow are
greater than 80% compared to running the same workflow via
direct Bash tool chaining