Follow Discord
Sweep 02 Oct 2026 · 18:55Z Build v2.1.288 509 read Stable v2.1.285 Latest v2.1.288 Next v2.1.288 Feeds RSS JSON llms.txt llms-full.txt Unofficial
One change · claude-code

Add components to a plugin changedplugins/components

Nearest release: v2.1.286, published 7 hours before upstream edited the page. Shown because the two are within 24 hours of each other. Nothing here says the release caused the edit.

Upstream edited this page at 1 Oct 2026 00:29 UTC, give or take a minute or two: the time comes from Anthropic’s own sitemap rather than from a commit. This site recorded the change at 1 Oct 2026 01:07 UTC.

Upstream edited
Recorded here
Lines+13added
Lines−2removed
From line 834 where the diff opens
First seen 25 Sep 2026 this site's first read of the page
Recorded edits8to this page, all time

The whole hunk

from line 834, old and new numbered
/
lines
from line 834
834834 
835835The server takes its name from the `name` in the bundle's manifest.
836836 
837A bundle's own manifest can declare settings the server needs from the user in a `user_config` block. A bundled server with a required setting that has no saved value doesn't start. The `/plugin` **Errors** tab shows `Bundled MCP server "<name>" was not started: it needs configuration`.
838 
839Users supply the values in one of two ways:
840 
841* **In `/plugin`**: select the plugin on the **Installed** tab and choose **Configure**
842* **At install, from the shell**: pass [`--config <server>.<key>=<value>`](/docs/en/plugins/cli-reference#plugin-install) to `claude plugin install`. Requires Claude Code v2.1.285 or later, and works only for a bundle packaged inside the plugin.
843 
837844For transports and authentication, see [MCP](/docs/en/mcp#plugin-provided-mcp-servers).
838845 
839846### LSP servers
from line 1030
10231030 
10241031### When the configuration dialog appears
10251032 
1026The dialog appears only in the interactive `/plugin` interface. It opens for any option that isn't set yet when the user does any of the following:
1033The dialog is part of the interactive `/plugin` interface. When the user does any of the following, it opens for any option that isn't set yet:
10271034 
10281035* Installs the plugin in `/plugin`
10291036* Runs `/plugin install <plugin>@<marketplace>` inside a session
from line 1038
10311038 
10321039To open the same dialog at any time, the user runs `/plugin configure <plugin>@<marketplace>`.
10331040 
1034The `claude plugin install` shell command never prompts for `userConfig` values. To set values from the shell, pass each one as `--config KEY=VALUE`. When options remain unset, the command prints a `userConfig options not yet set` line that names both ways to set them. [The `userConfig` dialog never appears](/docs/en/plugins/troubleshooting#the-userconfig-dialog-never-appears) quotes the line.
1041The VS Code extension's [Manage plugins dialog](/docs/en/vs-code#install-plugins) asks for unset options as a form after an install, and a gear icon on the plugin's row opens the form again with every option.
1042 
1043The `claude plugin install` shell command never prompts for `userConfig` values. To set values from the shell, pass each one as `--config KEY=VALUE` when you install, or pipe a JSON object to [`claude plugin configure --values-stdin`](/docs/en/plugins/cli-reference#plugin-configure) afterward.
1044 
1045When options remain unset, `claude plugin install` prints a `userConfig options not yet set` line. For the line's exact text, see [The `userConfig` dialog never appears](/docs/en/plugins/troubleshooting#the-userconfig-dialog-never-appears).
10351046 
10361047For the option fields, where each value is stored, how a component references a saved value, and which fields reject `${user_config.*}`, see [User configuration](/docs/en/plugins/manifest-reference#user-configuration).
10371048 
Feedback