If you run Open WebUI for yourself or a small group, the person who sets up the connection is the administrator, and everyone else simply switches the tool on. This guide is written for that administrator, and it covers the one setting in Docker that quietly breaks sign-in.
Who does what
Only an admin can add the connection. After that, each user enables the tool in their own chat and signs in to their own SpendixAI account. SpendixAI is the expense tracker we make for people in India, and each sign-in opens its own consent screen, where the person picks a workspace and a permission level. The admin never sees anyone's password, because SpendixAI uses Google sign-in and the standard OAuth flow.
Requirements
- Open WebUI version 0.6.31 or later, self-hosted.
- An account with admin rights.
- In Docker, a fixed WEBUI_SECRET_KEY value. Without it, stored OAuth tokens stop working after a restart.
- The server address from Developer → MCP connections.
Adding the connection
- In SpendixAI, copy the server address under Developer → MCP connections.
- In Open WebUI go to Settings, then Admin, then Integrations.
- Open External Tool Servers and choose Add Connection.
- Set Type to MCP (Streamable HTTP). Do not pick the OpenAPI type for an MCP server.
- Paste the address into Server URL and set Auth to OAuth 2.1.
- Choose Register Client, save, and restart if Open WebUI asks you to.
The only SpendixAI-specific value is the one this guide calls <your SpendixAI server address>. Register Client uses dynamic registration, so there is no client ID or secret to copy. Open WebUI also has a static OAuth 2.1 option for servers that need fixed credentials, which SpendixAI does not require.
Letting users sign in
Open WebUI advises against making OAuth 2.1 tools default model tools. Ask users to enable the tool per chat instead, so the browser sign-in can finish. Each user then chooses a permission preset on the SpendixAI screen.
A quick test before you tell anyone
Open a fresh chat yourself first. Enable the SpendixAI tool for that chat, complete the sign-in and ask for last month's total. Compare it with the SpendixAI dashboard. If the sign-in does not finish, check two things: that the tool is not set as a default model tool, and that the secret key is set if you run Docker. Once it works, send your users a short note explaining the Read only preset and how to disconnect.
Removing the connection from External Tool Servers takes it away from Open WebUI users. Each person can also end their own access from SpendixAI at any time.
Limiting what is exposed
The connection form includes a Function Name Filter List, which lets an admin choose which tool names are available. If you would like only the tools that read data, that is the place. The same form has optional fields for an OAuth Server URL, an OAuth Resource Parameter, OAuth Scopes and a Headers JSON box.
Summary of the settings
| Field | Value |
|---|---|
| Type | MCP (Streamable HTTP) |
| Server URL | The SpendixAI server address |
| Auth | OAuth 2.1, then Register Client |
| Docker | Set WEBUI_SECRET_KEY |
| Default tools | Leave off; users enable per chat |
| Approvals | Not covered on the page we read |
What we verified
The steps were checked against Open WebUI's own documentation in November 2026. That page did not describe whether the app asks for approval before a tool runs, so we cannot promise a prompt. Treat Read only and the filter list as your safeguards. Replies come from whichever model you have configured, so check key figures in the SpendixAI report before acting on them.
Prompts to try
- What did I spend on food last month compared with the month before?
- Which merchants did I pay most often this quarter?
- List my recurring charges and what each costs per year.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

