Skip to main content
Kremis loads configuration at startup using a 3-layer priority chain:
Higher-priority layers override lower ones, field by field. You can mix all three — for example, set stable values in kremis.toml and override secrets via env vars in CI.

kremis.toml

Place kremis.toml in the directory where you run kremis server or kremis-mcp. All fields are optional; omit any section you don’t need.
Copy the example template to get started:
kremis.toml is gitignored — your local configuration stays out of version control.

Environment Variables

Environment variables take precedence over kremis.toml. They are the recommended way to pass secrets and override settings in containerised environments. Setting KREMIS_API_KEY to an empty string explicitly disables authentication, even if api_key is set in kremis.toml.

Docker Example

Or pass at runtime:

CI / GitHub Actions

Sections Reference

[logging]

[api]

[security]

Never store api_key in kremis.toml in a shared repository. Use KREMIS_API_KEY or a secrets manager instead.

[cors]

[mcp]

This section is read by both kremis (for the MCP bridge URL reference) and kremis-mcp (to know which server to proxy requests to).
Last modified on May 9, 2026