{"version":"2.1.310","anchor":"mcp-server-config-gains-connectorid-mcp-call-blocks-restric","canonical_anchor":"tool-server-settings-accept-connectorid","heading":"MCP server settings gain connectorId and keep the configured command","tier":"use","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/mcp-server-config-gains-connectorid-mcp-call-blocks-restric","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### MCP server settings gain connectorId and keep the configured command\n\nMCP server settings accept a new connectorId field, stdio servers keep their original configuredCommand, and mcp_call refuses some servers' tools\n\n**Unclear.** Which servers other than remote-browser are restricted is not stated.\n\n**What**\n\nAn MCP server is an add-on that gives Claude extra tools. Its settings and handling changed in several ways:\n\n- `connectorId` is a new, internal field for an MCP server that names the claude.ai connector the server proxies. The settings parser accepts a non-empty string; a non-string or empty value is reported in the list of ignored settings.\n\n- For SDK MCP servers (servers supplied by a program that drives Claude Code through the SDK), `connectorId` applies when the server is first registered, like `timeout` and `disableAutoBackground`. A different `connectorId` sent again through initialize or `setMcpServers` is ignored, and the warning now names it.\n\n- For sdk-type configs, `connectorId` is now removed along with `tools` from the server result.\n\n- `configuredCommand`: when an MCP server config goes through environment-variable expansion, stdio servers (servers started as a local program) now keep their original command alongside the expanded one, and the server result reports it when it is found in the server's mcp_config.\n\n- `mcp_call` and the permission prompt tool now refuse tools of certain servers. For example, a permission prompt tool on the MCP server `remote-browser` is denied.\n\n- In one place the HTTP agent options are now built with `carriesOurToken` set to false.\n\n- The copy picker gained new footer styling and a header label, and the settings panel has a tweaked layout for its search line.\n\n**Why**\n\nProgram authors using the SDK should know that `connectorId` cannot be changed by re-sending initialize. The `mcp_call` change means a server such as `remote-browser` can no longer act as the tool that answers its own permission prompts.\n\n- Area: MCP\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: yes"}