Jan + SpendixAI
Jan is a local AI app whose documentation describes remote MCP servers with automatic OAuth. We could only verify the console route for SpendixAI, and the desktop screen for remote servers was not confirmed.
Connect in a few minutes.
In Jan, the documented route is the /mcp command in the agent console, followed by an Authenticate step.
Copy the server address
In SpendixAI open Developer → MCP connections and copy the MCP server URL.
Open the MCP list
In the Jan console run /mcp and press a to add a server.
Fill in the entry
Enter the name spendixai, choose http as the transport, then enter the server address when asked for the URL.
Switch it on
New servers start inactive. Select the entry and press Space to turn it on.
Authenticate
Select the server, press Enter and choose Authenticate. Jan prints a sign-in link and waits up to five minutes. Sign in to SpendixAI, pick your workspace and choose the Read only preset.
https://spendix-api.kriva.studio/mcpJan stores the token in a file called mcp_oauth.json with owner-only permissions, and the same configuration file is shared with Jan Desktop. If you set an Authorization header yourself, Jan skips OAuth.
What you need
- A Jan installation where you can reach the console
- A SpendixAI workspace
- The server address from Developer → MCP connections
- A browser for the sign-in step
Good to know
- The Jan Desktop page we read only shows servers that run a command, with fields for Command, Arguments and Environment Variables. A screen for adding a remote server there was not confirmed.
- The names of the form fields beyond name and transport, and the release that introduced remote OAuth, were not confirmed in the documentation we read.
- Jan Desktop asks for approval of each tool call by default, inline in the chat, showing the exact arguments. Leave Allow All MCP Tool Permissions off for SpendixAI.
- Jan does not accept pre-registered client credentials for remote OAuth. SpendixAI does not need them.
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.
Jan and SpendixAI.
Can I do this from the Jan desktop window?
We could not confirm a desktop screen for remote servers. The console route above is the one the documentation describes, and the configuration is shared with Jan Desktop.
Can I limit Jan to reading only?
Yes, in two places. Choose Read only on the SpendixAI consent screen, and in the agent console Jan offers a tool policy with read-only, deny and allow.
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 Jan’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 Jan into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.


