{"version":"2.1.318","anchor":"internal-build-gating-ae-on-repl-routed-mcp-tools-scrip","canonical_anchor":"internal-build-gating-ae-on-repl-routed-mcp-tools-scrip","heading":"More groundwork for running MCP tools from inside a REPL environment","tier":"soon","area":"REPL Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/internal-build-gating-ae-on-repl-routed-mcp-tools-scrip","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### More groundwork for running MCP tools from inside a REPL environment\n\nCode that presents MCP tools as callable inside a REPL environment gains further branches, all limited to a build check\n\n**Unclear.** It is not clear what the build check tests, so it is unknown whether any user can reach this.\n\n**What**\n\nMore code for a REPL-based tool setup is in this build. A REPL is an environment where code is typed and run one piece at a time. MCP tools are tools from outside services. Each of these runs only when a build check passes.\n\n- MCP tools are described as \"callable inside the REPL environment\" instead of always being described as available automatically.\n\n- Calls to helpers from inside scripts are tracked separately.\n\n- Claude Code records which tool call another call is running inside.\n\n- Spawned sessions get an option to choose a stand-in.\n\n**Why**\n\nThis looks like early scaffolding for running tools through scripts rather than as separate top-level tools.\n\n- Area: REPL Mode\n- Tier: Nothing to try yet\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no\n- Present in the build but not switched on"}