{"version":"2.1.300","anchor":"mcp-connect-can-request-toolslist-first-toolslistfirst","canonical_anchor":"mcp-connect-can-request-toolslist-first-toolslistfirst","heading":"MCP connections can ask for the tool list before setup finishes","tier":"use","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300\/e\/mcp-connect-can-request-toolslist-first-toolslistfirst","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.300","markdown":"### MCP connections can ask for the tool list before setup finishes\n\nA new connection option can make Claude Code request an MCP server's tool list early on some proxied connections, closing the link if the list stalls\n\n**Unclear.** How the `toolsListFirst` option gets set is not stated, so it is unclear whether a reader can turn it on.\n\n**What**\n\nWhen Claude Code connects to an MCP server (an outside tool server it talks to through the Model Context Protocol), it has a new option called `toolsListFirst`. When it is set, Claude Code asks the server for its list of tools before the server has finished its opening handshake. This applies to older-style connections that go through a proxy. If the tool list does not arrive within the usual connection timeout, the connection is closed. Before this, only a related option, `toolsListAhead`, existed.\n\n**Why**\n\nAsking for the tool list earlier can make MCP servers ready sooner at the start of a session on these proxied connections.\n\n- Area: MCP\n- Names: `toolsListFirst`, `toolsListAhead`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}