[alexluong]

Let operators who configure Outpost through environment variables only define MCP events, without a mounted file.

Stacked on #1182. Experimental.

Changes

1. Inline JSON. In the environment, an EXPERIMENTAL_MCP_EVENTS_SCHEMA value that starts with { is read as the definitions themselves, in the same events/list format and with the same strict JSON parsing and validation as a .json file. Any other value is a file path, as before.
2. Docs. The configuration table row, the config description and .env.example show the inline form.

Behavior changes

• Nothing changes unless the value starts with {; such a value used to be read as a file path and failed.
• In YAML a mapping is inline and a string is always a path, as in feat: add MCP event definitions in the events/list format and a catalog endpoint #1182.

Tests

internal/config tests (TestMCPEvents_InlineJSONInEnv): inline JSON loads (also with leading whitespace) and wins over the YAML mapping; invalid JSON and a missing events list are rejected with an error that names EXPERIMENTAL_MCP_EVENTS_SCHEMA; an empty list defines no events.

🤖 Generated with Claude Code

[alexluong]

Inline JSON for EXPERIMENTAL_MCP_EVENTS_SCHEMA is now part of #1182, which adds the key: #1182