config plugins validate

Validate plugin configuration

Synopsis

Validate plugin configuration structure and optionally check plugin binaries.

By default, validates config structure only (portable across environments). Use --check-binaries to also verify binaries exist (environment-specific).

mcpd config plugins validate [flags]

Examples

  # Validate config structure (portable)
  mcpd config plugins validate

  # Validate specific category
  mcpd config plugins validate --category=authentication

  # Check binaries exist (environment-specific)
  mcpd config plugins validate --check-binaries

  # Verbose output
  mcpd config plugins validate --verbose

Options

      --category category   Validate only this category (one of: audit, authentication, authorization, content, observability, rate_limiting, validation)
      --check-binaries      Check plugin binaries exist (environment-specific, NOT portable)
      --verbose             Show detailed validation info

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