What problem does it solve?
This Skill prevents large MCP tool schemas from ballooning your LLM prompt context by routing work through a single, token-efficient Python execution bridge instead of repeatedly loading many server tool definitions.
Core Features & Use Cases
- Constant token overhead: keeps prompt size near-constant (~200 tokens) regardless of how many MCP servers you connect.
- Discovery-first MCP proxying: dynamically queries tool schemas and searches docs only when needed, so you don’t pay the context cost upfront.
- Rootless, sandboxed execution: runs Python in rootless containers with hardened settings (no network, read-only root filesystem) to reduce risk while enabling practical automation.
- Persistent sessions: maintains variables and MCP client state across calls within the same session for iterative workflows.
Quick Start
Configure Claude Desktop to use a single MCP server called code-execution, then ask it to run a Python snippet that discovers the needed MCP tools and performs the task (for example, fetch data from a configured server, transform it in Python, and write results back).