Skip to main content

Overview

Configuration commands manage MCP configurations, servers, and their associated guardrails policies. Each configuration is a collection of MCP servers with their settings.

Configuration Management

List Configurations

List all MCP configurations in the system.

Add Configuration

Create a new MCP configuration.
string
required
Name for the new configuration (must be unique)

Get Configuration

Retrieve details of a specific configuration.
string
Configuration name
string
Configuration UUID
You must provide either --config-name or --config-id, not both.

Copy Configuration

Duplicate an existing configuration with a new name.
string
required
Name or ID of the source configuration
string
required
Name for the new configuration copy

Rename Configuration

Change the name of an existing configuration.
string
required
Current configuration name or ID
string
required
New name for the configuration

Remove Configuration

Delete a configuration (must not be in use by any projects).
You cannot remove a configuration that is assigned to projects. Unassign it from all projects first.

Server Management

List Servers

List all servers in a configuration.

Add Server

Add a new MCP server to a configuration.
string
required
Configuration name or ID
string
required
Unique server name within the configuration
string
required
Command to execute (e.g., python, npx, node)
string
Comma-separated command arguments
json
Environment variables as JSON object
json
Tool configuration as JSON object
string
Server description
json
Input guardrails configuration
json
Output guardrails configuration

Get Server

Retrieve details of a specific server.

Update Server

Modify server configuration.

Remove Server

Delete a server from configuration.

Remove All Servers

Remove all servers from a configuration.

Guardrails Management

Update Input Guardrails

Configure input protection for a server.
string
required
Configuration name or ID
string
required
Server name
json
Policy configuration as JSON string
string
Path to JSON file containing policy
Provide either --policy or --policy-file, not both.

Update Output Guardrails

Configure output protection for a server.
output_policy.json:

Update Both Guardrails

Update input and output guardrails together.
json
Input policy as JSON string
string
Path to input policy JSON file
json
Output policy as JSON string
string
Path to output policy JSON file

Plugin Configuration

Set Enkrypt API Key

Configure the API key for Enkrypt guardrails.

Get Enkrypt API Key

Retrieve the configured Enkrypt API key.

Configure Telemetry

Manage OpenTelemetry settings.
boolean
Enable or disable telemetry
string
OpenTelemetry collector URL
boolean
Allow insecure connections (for local development)

Utility Commands

List Projects Using Config

Show which projects are using a configuration.

Validate Configuration

Check configuration structure and integrity.

Export Configuration

Export configuration to a JSON file.

Import Configuration

Import configuration from a JSON file.

Search Configurations

Search for configurations by name or server name.

Best Practices

  • Use descriptive config names: production-web-servers vs config1
  • Include environment in name: dev-config, staging-config, prod-config
  • Use consistent naming across related configs
  • Group related servers in the same configuration
  • Separate development and production servers
  • Document server purposes in descriptions
  • Enable guardrails for production servers
  • Test policies in development first
  • Use PII redaction for sensitive data
  • Regular policy reviews and updates
  • Export configs for backup
  • Store exported configs in version control
  • Test imports before applying to production
  • Document configuration changes

Common Workflows

Setup Production Configuration

Clone Configuration for Testing