docs/features/settings-page.md
The Web UI Configuration page (/ui/settings) presents mcpproxy's config as
friendly, prioritized form sections instead of raw JSON:
tool_response_mode
for Retrieve, direct_tool_response_mode for Direct), tool limits, response
limit, call timeout, log level, telemetry, prompts.Each section saves only the fields you changed via PATCH /api/v1/config, a
partial deep-merge that routes through the normal validate → persist → hot-reload
pipeline. Because the merge starts from the live config and overlays just your
changes, unrelated values and masked secrets (API key, secret headers) are never
overwritten.
Fields that need a restart (listen, api_key, routing_mode, tls.*,
code_execution_pool_size, and server_edition.enabled on the server edition)
show a restart badge — the two response-detail modes deliberately carry no
badge, because they hot-reload; sensitive changes (reveal secret headers, disabling
quarantine/management, binding to a non-loopback address) require an explicit
confirmation before they apply.
# Equivalent API call — change one field, everything else preserved
curl -X PATCH -H "X-API-Key: $KEY" -H 'Content-Type: application/json' \
-d '{"quarantine_enabled": false}' http://127.0.0.1:8080/api/v1/config
Complex lists/maps (Docker image map, custom detection patterns, environment
vars) and mcpServers / registries are managed on their own pages or the Raw
JSON tab. See the configuration reference for the full option list.