Configuration¶

MCC uses Dynaconf for configuration. Settings are loaded in this order, with later sources taking precedence:

1. mcc/settings.yaml — built-in defaults (do not edit)
2. settings.local.yaml — your local overrides (not committed)
3. Environment variables with the MCC_ prefix

Local overrides¶

Create settings.local.yaml in your project root to override any setting:

auth: github
tools:
  - mytools.yaml

elasticsearch_url: https://my-es-host.internal:9200

Environment variables¶

Any setting can be set via environment variable using the MCC_ prefix. Nested keys use double underscores:

MCC_AUTH=dev-admin
MCC_ELASTICSEARCH_URL=https://my-es-host.internal:9200

Environment variables always override file-based settings.

MCC_SETTINGS_FILES¶

A semicolon-separated list of additional settings files to load, appended after settings.local.yaml. Use this to layer in toolset configs without modifying your local overrides file:

MCC_SETTINGS_FILES=toolsets/contrib/settings.yaml;toolsets/osint/settings.yaml

Each file is merged with dynaconf_merge: true, so tools lists are additive.

MCC_TOOL_FILES¶

A semicolon-separated list of tool YAML files, directories, or glob patterns to load in addition to those declared in settings.tools. Use this to inject extra tools at load time without modifying settings files:

MCC_TOOL_FILES=/etc/mcc/tools;/opt/custom/*.yaml

Paths are resolved exactly like entries in the tools setting — directories load all *.yaml files (flat), and glob patterns expand recursively. These tools are loaded after the settings-declared tools and participate in hot-reload.

Environments¶

Dynaconf supports named environments. MCC ships with development (debug logging) and production (verbose log format, INFO level) profiles. Set the active environment with:

ENV_FOR_DYNACONF=production

Defaults to development unless overridden.

Settings reference¶

auth¶

Authentication backend. Default: dev-admin (no auth, dev only).

See Auth Backends for backend-specific configuration.

tools¶

List of YAML tool files or directories to load at startup. Default: [].

tools:
  - mytools.yaml                  # single file
  - path/to/tools_dir             # all *.yaml files in directory (flat)
  - path/to/tools/**/*.yaml       # glob pattern (recursive supported)

embedding_model¶

The fastembed model used for semantic search. Default: BAAI/bge-small-en-v1.5.

embedding_model: BAAI/bge-small-en-v1.5

The model is downloaded on first use and cached locally by fastembed. Changing this requires a server restart to re-index tools.

Elasticsearch¶

The connection is configured with a single elasticsearch_url (env var MCC_ELASTICSEARCH_URL). Scheme, host, port, and basic-auth credentials all come from the URL:

MCC_ELASTICSEARCH_URL=https://elastic:pass@host:9200?verify_certs=false

Append ?verify_certs=false to allow self-signed/untrusted certificates over https (dev only).

oauth¶

Required for all OAuth proxy backends (github, google, azure, etc.).

Some backends require additional keys — see Auth Backends for per-provider details. All keys are settable via env vars: MCC_OAUTH__BASE_URL, MCC_OAUTH__CLIENT_ID, MCC_OAUTH__CLIENT_SECRET.

jwt¶

Required when auth: jwt (generic OIDC / JWKS verification).

server¶

HTTP server settings.

When a tool response exceeds response_max_size, MCC truncates the text content and appends [Response truncated due to size limit] rather than returning an error. Override via environment variable:

MCC_SERVER__RESPONSE_MAX_SIZE=10000000  # 10 MB

logging¶

Standard Python logging.config.dictConfig dict. The built-in config writes to stderr. Override the log level per environment or set it directly:

logging:
  loggers:
    mcc:
      level: DEBUG