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:

  1. 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.

  2. Open the profile menu at the bottom of the sidebar.
  3. Select Settings.
  4. Scroll the settings sidebar to the Admin section.
  5. Select Integrations under Tools.
  6. 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.

  7. Enter Time Tools in Name.
  8. Enter time_tools in ID (optional).
  9. 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.

  10. 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.

  11. Expand Advanced.
  12. 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.

  13. 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.

  14. Connect the server with the dialog's Save button.
  15. Close Settings with Back.
  16. Reload Open WebUI in the browser to refresh the chat's tool list.
  17. Start a New Chat from the sidebar.
  18. Open the model picker in the composer.
  19. 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.

  20. Open the Integrations button beside + in the composer.
  21. Open Tools in the integrations menu.
  22. Enable Time Tools for the chat.
  23. 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.

  24. Send the prompt with Enter.
  25. 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.

Share this guide