OBJECT
Connection namespace. Platform names: ‘inbox’, ‘booking’, ‘wiki’; anything else is a custom connection. Served tools are exposed to the agent as ‘{name}__{tool_name}’ (e.g. ‘booking__create_booking’).
Streamable-HTTP MCP endpoint — only meaningful for custom connections and the gateway (which resolves its platform default from MCP_GATEWAY_URL when empty). The RevVue product rows (inbox/booking/wiki) are policy cards and are never dialed.
Kill switch for this connection — when False none of its tools are loaded or bound.
Server-side tool names this assistant may use (original or namespaced form accepted). Empty = all tools the server offers.
Operator-facing description of what this connection provides.
How requests to this server authenticate. ‘platform’ = the tenant-scoped platform JWT headers (raw JWT on Authorization + tenant header — the contract every platform MCP server uses); ‘none’ = no auth headers (open/externally-managed servers); ‘bearer’ = ‘Authorization: Bearer {bearer_token}’ with the operator-provided token below. Custom external servers typically use ‘none’ or ‘bearer’.
Operator-provided static token, used only when auth_mode=‘bearer’. Sent as ‘Authorization: Bearer {token}’ on every request to this server.
Prefix served tool names with ‘{name}’ (the default). Aggregators that already serve namespaced names — the RevVue MCP gateway serves inbox, cognee__, analytics__* — set False so names pass through as served instead of double-prefixing (‘gateway__inbox__…’).