n8n + SpendixAI
n8n can call a remote MCP server from an AI Agent or from a standalone MCP Client node. SpendixAI connects through an MCP OAuth2 credential, so nothing secret is pasted into the workflow.
Connect in a few minutes.
In n8n, SpendixAI is added through the MCP Client Tool node with an MCP OAuth2 credential.
Add the node
Add the MCP Client Tool sub-node to an AI Agent, or use the MCP Client node on its own.
Enter the server address
Paste the SpendixAI server address from Developer → MCP connections into the endpoint field of the node.
Set authentication
Set Authentication to OAuth2 and create an MCP OAuth2 credential, named for example spendixai. Leave Use Dynamic Client Registration switched on, which is the default.
Sign in
Use the credential’s connect button. A SpendixAI page opens where you sign in, choose your workspace and pick a permission preset. Start with Read only.
Limit the tools
In Tools to Include choose Selected, and tick only the read tools you want the workflow to use.
https://spendix-api.kriva.studio/mcpIf a server does not support dynamic client registration, the credential also accepts an Authorization URL, Access Token URL, Client ID and Client Secret. SpendixAI does not need them.
What you need
- An n8n instance with the AI Agent node, or the MCP Client node
- A SpendixAI workspace
- The server address from Developer → MCP connections
Good to know
- The page for the MCP Client Tool node documents only an SSE endpoint field, so we could not confirm that it works with a Streamable HTTP server. The separate MCP Client node lists a Server Transport option, but the documentation we read did not say which options it offers.
- The label of the credential’s sign-in button was not confirmed in the documentation we read, and neither was a minimum n8n version or plan.
- n8n does not describe an approval step. Workflows run tools on their own, so keep the SpendixAI connection Read only and add your own approval step before any workflow that writes.
- Tools to Include accepts All, Selected or All Except. Selected is the safest choice for finance data.
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.
n8n and SpendixAI.
Will n8n ask before using a SpendixAI tool?
The documentation does not describe a prompt. Workflows run unattended, so restrict the tools with Tools to Include and use the Read only preset.
Which transport does it use?
We could not confirm this for the MCP Client Tool node, which documents an SSE endpoint. Check the node’s Server Transport options on your n8n version before you build on it.
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 n8n’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 n8n into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.


