{"version":"2.1.318","anchor":"mcp-tool-wait-description-for-repl-mode","canonical_anchor":"mcp-tool-wait-description-for-repl-mode","heading":"Waiting for MCP servers can describe tools as available inside the REPL","tier":"internal","area":"REPL Mode","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318\/e\/mcp-tool-wait-description-for-repl-mode","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.318","markdown":"### Waiting for MCP servers can describe tools as available inside the REPL\n\nIn one mode, the tool that waits for MCP servers says their tools become callable inside the REPL instead of joining the main tool list\n\n**Unclear.** It is not known what switches this REPL mode on, so readers cannot tell whether they will see it.\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools. Claude Code has a tool that waits for these servers to finish connecting.\n\nIn a particular mode, the description of that waiting tool now tells Claude something different. Instead of saying the servers' tools will be added to its main list of tools, it says they become callable inside the REPL environment. A REPL is an interactive place where code is run line by line.\n\nRelated additions:\n\n- An error for when a built-in MCP server running inside Claude Code reaches beyond its own tools in this mode\n\n- A waiting step that follows status lines while it polls\n\n**Why**\n\nIt points to a way of routing MCP tools through the REPL that is still being built.\n\n- Area: REPL Mode\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}