config plugins add
mcpd config plugins add¶
Add a new plugin entry to a category
Synopsis¶
Add a new plugin entry to a category. The configuration is saved automatically.
The plugin name must exactly match the name of the plugin binary file.
This command creates new plugin entries only. If a plugin with the same name already exists in the category, the command fails with an error. To update an existing plugin, use the 'set' command.
mcpd config plugins add <plugin-name> [flags]
Examples¶
# Add new plugin with all fields
mcpd config plugins add jwt-auth --category=authentication --flow=request --required
# Add plugin with multiple flows
mcpd config plugins add metrics --category=observability --flow=request --flow=response --commit-hash=abc123
# Add without required flag (defaults to false)
mcpd config plugins add rbac --category=authorization --flow=response
Options¶
--category category Specify the category (one of: audit, authentication, authorization, content, observability, rate_limiting, validation)
--commit-hash string Optional, commit hash for runtime version validation
--flow stringArray Flow during which, the plugin should execute (request, response) (can be repeated)
--required Optional, mark plugin as required
Options inherited from parent commands¶
--config-file string path to config file (default ".mcpd.toml")
--log-level string log level for mcpd logs (default "info")
--log-path string log file path to use for log output
--runtime-file string path to runtime (execution context) file that contains env vars, and arguments for your MCP servers (default "/home/runner/.config/mcpd/secrets.dev.toml")
SEE ALSO¶
- mcpd config plugins - Manage plugin configuration