Dify + SpendixAI
Dify can add a remote MCP server over HTTP and handles the OAuth sign-in with dynamic client registration. Add SpendixAI once, then use its tools in your apps.
Connect in a few minutes.
In Dify, SpendixAI is added from the MCP tab under Integrations → Tools.
Open the MCP tab
In Dify go to Integrations → Tools and open the MCP tab, then add a server.
Enter the details
Paste the SpendixAI server address from Developer → MCP connections, give the server a name such as spendixai and choose a short, unique server identifier.
Authorize
Leave dynamic client registration on. Dify opens the SpendixAI sign-in, where you choose your workspace and a permission preset. Start with Read only.
Use the tools
Once the tools are imported, use them as a Tool node or an Agent node in Workflow and Chatflow apps, or in an Agent app.
https://spendix-api.kriva.studio/mcpIf a server does not support dynamic client registration, Dify takes a Client ID and Client Secret and shows a redirect address to register. Custom headers can carry a static token. SpendixAI needs neither.
What you need
- A Dify workspace that can add MCP servers
- A SpendixAI workspace
- The server address from Developer → MCP connections
Good to know
- Changing the server identifier later breaks any app that refers to it, so choose it with care.
- The Japanese version of the documentation limits the identifier to 24 characters of lowercase letters, digits, underscores and hyphens, and gives the button wording as Add MCP Server (HTTP). We could not confirm either on the English page, so your screen may differ.
- Dify’s documentation names HTTP as the only transport. A required plan or version was not stated.
- No approval step is described. Apps and agents call tools on their own, so keep the SpendixAI connection Read only.
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.
Dify and SpendixAI.
Do I need to register an OAuth client?
No. Dify has dynamic client registration switched on by default, and SpendixAI supports it.
Will my Dify agent ask before it runs a tool?
The documentation does not describe a prompt, so rely on the Read only preset and on which tools you attach to the app.
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 Dify’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 Dify into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.


