What
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.
- The value is a JSON map in the same shape as the
enabledPluginssetting. - Only named plugins from marketplaces Claude Code already knows are turned on.
- Claude Code reads the variable and then removes it, so it is not passed on further.
- It is ignored when Claude Code runs in hermetic mode.
claude mcp serve now also checks your organisation's configuration requirements when it starts.
Why
Tools that start Claude Code as an MCP server can now decide which plugins it loads, without editing settings files by hand.
Names in the bundleclaude mcp serve
The entry above is what we published on the day. These lines were added later, as Anthropic's own pages caught up, and they sit beside the original rather than replacing it.
Confirmed since
Anthropic's documentation has since written up claude mcp serve, on Connect Claude Code to tools via MCP.
A `backgroundOutputPath` field in a Bash or PowerShell result from `claude mcp serve` means the call left its command running [in the background](/docs/en/tools-reference#background-commands). A command runs in the background when your cli…mcp see the edit
One source agreesOne thing we can check says the same as this entry.
Anthropic's documentation agrees
Anthropic's documentation has since written up claude mcp serve, on Connect Claude Code to tools via MCP.