Configuring the endpoint v7

Set endpoint parameters in postgresql.conf or with ALTER SYSTEM. AIDB registers every endpoint setting as an ordinary Postgres parameter. A change to edb.endpoints_enabled needs a Postgres restart. Every other parameter takes effect on SELECT pg_reload_conf();, unless no server switch was on when Postgres started. In that case, turning one on needs a restart too.

Three on/off switches decide what runs. A server runs when its own switch is on and edb.endpoints_enabled is on, so out of the box nothing runs:

• edb.endpoints_mcp_enabled and edb.endpoints_otlp_enabled turn the MCP server and the OTLP/HTTP server on or off. Both default to off.
• edb.endpoints_enabled is a master off switch, default on. Set it to off to disable every server, whatever the other two say.

The supervisor starts when a server switch is on at Postgres startup. If both are off then, turning one on later needs a restart.

General settings

These apply to every server the endpoint process runs, MCP and the OTLP server:

MCP settings

The edb.endpoints_mcp_* settings apply to the MCP server only. When one that has a general counterpart is empty, the general setting is used.

OTLP server settings

The OTLP/HTTP server has only a switch and a port of its own. It takes its host, TLS pair, and databases from the general settings.

OAuth settings

To accept bearer tokens from MCP clients and OTLP senders, configure the edb.endpoints_oauth_* and edb.endpoints_mcp_oauth_* settings. See Authenticating with OAuth.

Values with no parameter

The supervisor derives a few settings from the Postgres server itself:

• The endpoint connects to Postgres through the first entry in unix_socket_directories, falling back to 127.0.0.1, on the server's own port, with sslmode=disable.
• Each agent connection has a 10 second connection timeout, and a statement_timeout and idle_in_transaction_session_timeout of 30 seconds. Postgres cancels a tool that runs longer, and the timeout error passes through to the client.
• The endpoint's environment is cleared except for RUST_LOG, which is passed through from the postmaster's environment. See Logging.

What happens on a reload

After a reload, the supervisor compares the new values with the running endpoint:

• A change to a server switch (edb.endpoints_mcp_enabled or edb.endpoints_otlp_enabled), command path, host, port, database, or TLS path, or to any OAuth parameter, whether general, MCP, or OTLP, stops the running endpoint and starts a new one with the new values. In-flight calls on the old process get up to 10 seconds to finish.
• A change to edb.endpoints_restart_max or edb.endpoints_restart_window_secs resets the restart budget without touching the running endpoint.
• Any other change leaves the endpoint running. It reads its TLS certificates and keys again from the same paths, so a renewed certificate takes effect without a restart. See Serving remote clients.
• Any reload wakes an idle supervisor and lets it try again. See Restart budget.

Deprecated settings

These settings configure the whole process rather than MCP. If you set one, it still takes precedence over its replacement, and the supervisor logs a warning. Replace each with its new name: