{"version":"2.1.304","anchor":"mcp-serve-http-enabled-plugins-via-env-org-config-gate-a","canonical_anchor":"mcp-serve-http-enabled-plugins-via-env-org-config-gate-a","heading":"Choose which plugins load when Claude Code runs as an MCP server","tier":"use","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304\/e\/mcp-serve-http-enabled-plugins-via-env-org-config-gate-a","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.304","markdown":"### Choose which plugins load when Claude Code runs as an MCP server\n\n`CLAUDE_CODE_MCP_SERVE_ENABLED_PLUGINS` lets a program that launches `claude mcp serve` pick which plugins are turned on\n\n**What**\n\n`claude mcp serve` runs Claude Code as an MCP server, so another program can use its tools. That program can now set the environment variable `CLAUDE_CODE_MCP_SERVE_ENABLED_PLUGINS` to choose which plugins (add-ons that extend Claude Code) are turned on.\n\n- The value is a JSON map in the same shape as the `enabledPlugins` setting.\n\n- Only named plugins from marketplaces Claude Code already knows are turned on.\n\n- Claude Code reads the variable and then removes it, so it is not passed on further.\n\n- It is ignored when Claude Code runs in hermetic mode.\n\n`claude mcp serve` now also checks your organisation's configuration requirements when it starts.\n\n**Why**\n\nTools that start Claude Code as an MCP server can now decide which plugins it loads, without editing settings files by hand.\n\n- Area: MCP\n- Names: `claude mcp serve`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}