config plugins set

Sets top-level config for all plugins, or config for a specific plugin entry

Synopsis

Sets top-level config for all plugins (--dir), or updates config for a specific plugin entry (--category, --name, --flow). Cannot mix both modes.

Top-level mode sets configuration that applies to all plugins, such as the directory where plugin binaries are located.

Plugin entry mode updates config for an existing plugin. When updating, only the provided flags are changed (partial update).

mcpd config plugins set [flags]

Examples

  # Set plugin directory
  mcpd config plugins set --dir=/path/to/plugins

  # Update existing plugin entry (partial update)
  mcpd config plugins set --category=authentication --name=jwt-auth --flow=request --flow=response

Options

      --category category    Plugin category (plugin entry only, one of: audit, authentication, authorization, content, observability, rate_limiting, validation)
      --commit-hash string   Optional, commit hash for version validation (plugin entry only)
      --dir string           Directory path for location of plugin binaries (top-level config only)
      --flow stringArray     Flow during which the plugin should execute (request, response) (can be repeated, plugin entry only)
      --name string          Plugin name (plugin entry only)
      --required             Optional, mark plugin as required (plugin entry only)

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

Auto generated by spf13/cobra on 14-Aug-2026