{"version":"2.1.292","anchor":"sdk-mcp-server-settings-forwarded-as-a-whole-object","canonical_anchor":"sdk-mcp-server-settings-forwarded-as-a-whole-object","heading":"MCP servers set up through the SDK pass on all their settings","tier":"notice","area":"SDK","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/sdk-mcp-server-settings-forwarded-as-a-whole-object","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### MCP servers set up through the SDK pass on all their settings\n\nMCP servers defined through the SDK now pass their whole settings object to Claude Code, not only a timeout\n\n**Unclear.** Which settings besides the timeout can be included is not stated.\n\n**What**\n\nThe SDK lets developers run Claude Code from their own programs, and they can define MCP servers there. MCP servers are outside programs that give Claude extra tools. Before, only a server's timeout was passed on to Claude Code. Now the whole settings object is passed on whenever it is not empty.\n\n**Why**\n\nPer-server settings other than the timeout can now reach Claude Code.\n\n- Area: SDK\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}