{"version":"2.0.22","anchor":"mcp-server-user-configuration-support","canonical_anchor":"mcp-server-user-configuration-support","heading":"MCP Server User Configuration Support","tier":null,"area":null,"scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.0.22\/e\/mcp-server-user-configuration-support","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.0.22","markdown":"### MCP Server User Configuration Support\n\n**What:** Plugins can now request user-provided configuration values (API keys, paths, settings) through structured schemas defined in their manifest files.\n\n**How to use:**\n\n`# When adding a plugin that requires configuration: claude mcp add my-plugin # If the plugin has user_config requirements, you'll see: # Configure my-plugin server # Field 1 of 3: API Key # [Enter your value] # Or configure an existing plugin: claude mcp configure my-plugin server-name` **Details:**\n\n- Plugins define `user_config` schemas in manifest.json with field types (string, number, boolean, file, directory)\n- Interactive CLI prompts collect configuration values with validation\n- Sensitive fields (API keys, tokens) are masked during input\n- Configuration persisted to `~\/.claude\/userSettings.json` under `pluginConfigs`\n- Server configs support variable substitution using `${user_config.fieldName}` syntax\n- Validation ensures required fields are provided and types match schema\n- **Evidence**: `CF1()` at line 280192, `q7B()` at line 280048, `fOQ()` at line 447320"}