{"version":"2.1.285","anchor":"plugin-install-config-reaches-bundled-mcp-server-config","canonical_anchor":"plugin-list-json-gains-data-size-and-per-plugin-fields","heading":"Plugin command line: configure options without the menu, set bundled MCP server settings, and see data size","tier":"use","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/plugin-install-config-reaches-bundled-mcp-server-config","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Plugin command line: configure options without the menu, set bundled MCP server settings, and see data size\n\nNew `claude plugin configure`, `plugin install --config` reaching bundled MCP server settings, and `plugin list --data-size` for scripts\n\n**What**\n\nMore plugin setup can now be done from the command line, without the interactive `\/plugin` menu. A plugin's options, called `userConfig`, are the settings it asks you for, such as an API key.\n\n- `claude plugin configure <plugin>`: a new subcommand. Run on its own, it shows a plugin's options and which are unset. With `--values-stdin`, it reads a JSON object of single-line strings from standard input and saves them, for example `claude plugin configure <plugin> --values-stdin < values.json`. Options you leave out keep their values. `--json` gives machine-readable output, and `--cowork` is also accepted. Input is capped at 256 KB and each value at 64 KB. Values are checked against the plugin's option list, and sensitive values are hidden in error output.\n\n- `plugin install --config KEY=VALUE`: can be repeated, and a pair with no key is an error. It can now also set the own `user_config` field of a bundled `.mcpb` MCP server, written as `<server>.<key>=<value>`. Before, it accepted only options declared in the plugin's manifest. A key that is undeclared, or declared by more than one bundled server, is an error. After installing, the command lists options left unset and MCP servers that still need configuration.\n\n- `claude plugin list --json --data-size`: takes a plugin id, or nothing for all plugins, and reports `dataDirSize` and `dataDirUnreadable`. Each entry also gains `projectEnabled` and `hasUserConfig`. Naming a plugin that is not installed exits with an error.\n\n**Why**\n\nScripts can now install a plugin, fill in its settings, secrets included, and check how much disk space its data folder uses. Before, setting options was only possible through the interactive menu.\n\n- Area: Plugins\n- Names: `--config`\n- Tier: Use it now\n- Useful: 5\/5\n- Signal: 2\/5"}