{"version":"2.1.310","anchor":"plugin-mcp-configs-compute-an-extra-value-for-stdio-servers","canonical_anchor":"plugin-mcp-configs-compute-an-extra-value-for-stdio-servers","heading":"Plugin MCP servers that run locally now keep an earlier copy of their settings","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310\/e\/plugin-mcp-configs-compute-an-extra-value-for-stdio-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.310","markdown":"### Plugin MCP servers that run locally now keep an earlier copy of their settings\n\nFor plugin MCP servers run as local programs, Claude Code now also keeps their settings as they were before the environment is filled in\n\n**Unclear.** It is not clear what the extra copy of the settings is used for or whether it changes anything a user sees.\n\n**What**\n\nPlugins can bring MCP servers, which are add-on services that give Claude extra tools. Some run as a local program on your machine (stdio servers). For these, Claude Code used to produce only the fully filled-in settings. It now also keeps a second copy taken before the server's environment variables are finalised. Plugin MCP servers reached over the network (SSE or HTTP) now go through an extra processing step when plugins are listed.\n\n**Why**\n\nYou set up plugin MCP servers the same way as before. This changes how Claude Code handles their settings behind the scenes.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}