Open WebUI + SpendixAI
Open WebUI is a self-hosted chat interface with built-in MCP support. An administrator adds SpendixAI once, and each user then signs in to their own SpendixAI account when they use it.
Connect in a few minutes.
In Open WebUI, SpendixAI is added by an admin under External Tool Servers using the MCP type with OAuth 2.1.
Copy the server address
In SpendixAI open Developer → MCP connections and copy the MCP server URL.
Open the admin settings
As an admin go to Settings → Admin → Integrations, then External Tool Servers, and choose Add Connection.
Choose the MCP type
Set Type to MCP (Streamable HTTP) and paste the server address into Server URL. Do not use the OpenAPI type for MCP.
Set OAuth 2.1 and register
Set Auth to OAuth 2.1 and choose Register Client. Save the connection, restarting if Open WebUI asks you to.
Sign in from a chat
In a chat, switch the tool on and complete the SpendixAI consent screen in the browser. Pick your workspace and the Read only preset.
https://spendix-api.kriva.studio/mcpThe connection form also has optional fields: an OAuth Server URL, an OAuth Resource Parameter, OAuth Scopes (Discovered or Custom), a Headers JSON field and a Function Name Filter List. A static OAuth 2.1 option exists too, for servers that need a fixed Client ID and secret. SpendixAI does not.
What you need
- A self-hosted Open WebUI at version 0.6.31 or later, and an account with admin rights
- A SpendixAI workspace
- In Docker, a WEBUI_SECRET_KEY value set, or OAuth tokens stop working after a restart
Good to know
- Open WebUI advises against making OAuth 2.1 tools default model tools. Users should enable the tool per chat so the browser sign-in can finish.
- Whether Open WebUI asks for approval before each tool call was not covered on the MCP page we read.
- The Function Name Filter List lets an admin choose which tool names are exposed, which helps if you want to offer only the tools that read data.
- Only an administrator can add the connection, so a user of a shared instance cannot do this alone.
Questions to start with.
These need only read access. Add records or upload statements once you have moved to a broader preset.
Start read only. Widen it later.
Ask about transactions, summaries and reports. Nothing can be added, changed or uploaded.
Ask questions, add expenses and upload statements or receipts.
Everything above, plus categorisation rules and insights. Billing and member settings stay in the console.
Open WebUI and SpendixAI.
Why does my sign-in stop working after a restart?
In Docker, Open WebUI needs a fixed WEBUI_SECRET_KEY. Without it the stored OAuth tokens break when the container restarts.
Does every user share one SpendixAI login?
Open WebUI’s guidance is for users to enable the tool in their own chat so the browser sign-in can complete for them.
Do I need to paste an API key?
No. The connection uses your SpendixAI sign-in and a consent screen, with dynamic client registration, so there is no secret to copy into a config file.
Can I keep the connection read only?
Yes. Read only is the recommended preset, and you can grant more access later or disconnect the assistant at any time from Developer → MCP connections.
Setup steps were checked against Open WebUI’s own documentation in November 2026. Menus and commands change, so if a step does not match what you see, follow the vendor’s current guide.
Bring Open WebUI into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.


