Chat models need an explicit interface to query services beyond their training data. An OpenAPI tool server gives Open WebUI a schema describing callable HTTP operations, so a chat can request live data from that service.
Admin-managed tool servers are contacted by the Open WebUI backend. Browser access alone does not establish that connection, and the selected chat model needs native tool-calling support to choose an operation and use its response.
A schema describes capabilities without enforcing permissions. Authentication and authorization still belong to the tool server, and tool requests can disclose conversation data to it. A private read-only time service provides a low-risk first test before granting access to services that change records or execute commands.
Steps to connect an OpenAPI tool server in Open WebUI:
- Inspect the tool server's OpenAPI document for the read-only operation you intend to expose.
$ curl --fail-with-body --silent --show-error "https://tools.example.com/openapi.json"
The Open WebUI reference Time server provides a read-only UTC lookup at GET /get_current_utc_time, identified by get_current_utc_get_current_utc_time_get. Its complete schema describes the other time operations and their inputs and responses.
The server must already be running at its own reachable address. https://tools.example.com represents that address.
Tool: OpenAPI Operation Coverage Checker compares schema operations with a request inventory; it does not contact the server. - Open the profile menu at the bottom of the sidebar.

- Select Settings.

- Scroll the settings sidebar to the Admin section.

- Select Integrations under Tools.

- Click the plus beside External Tool Servers to open Add Connection.
The default Type is OpenAPI. MCP is a separate protocol, covered by How to connect an MCP server in Open WebUI.
- Enter Time Tools in Name.

- Enter time_tools in ID (optional).

- Enter the backend-reachable server address in URL.
For a containerized backend, localhost refers to that container. A server on a Docker Desktop host needs an address such as http://host.docker.internal:8000; a server on the same Docker network can use its service name.
- Select None under Auth for the private read-only time server.
None sends no credentials. An authenticated server needs its actual authentication mode and credentials; this choice does not bypass its access controls.
- Expand Advanced.

- Enter /openapi.json in openapi.json URL or Path under OpenAPI Spec.
URL is the schema source type. The resolved address below the field should point to the server's actual OpenAPI document.
- Click Verify Connection beside the server URL.
Connection successful confirms that the backend fetched the schema. It does not establish that the model can call an operation. A failed check can indicate an incorrect URL, schema path, credentials, or backend network access.
- Connect the server with the dialog's Save button.

- Close Settings with Back.

- Reload Open WebUI in the browser to refresh the chat's tool list.

- Start a New Chat from the sidebar.

- Open the model picker in the composer.

- Select a connected model with native function calling enabled.
company-chat is the selected model's display name here. A model that only produces text can describe a tool call without executing one.
- Open the Integrations button beside + in the composer.

- Open Tools in the integrations menu.

- Enable Time Tools for the chat.

- Enter a request for the tool's current UTC value in the composer.
Use the Time Tools server to get the current UTC time. Report the exact UTC value returned by the tool.
- Send the prompt with Enter.

- Confirm that the chat displays the UTC timestamp returned by Time Tools.
A matching GET /get_current_utc_time request in the tool server's log distinguishes an executed lookup from a guessed answer. The returned timestamp changes on each call.