Zapier MCP Client + SpendixAI
Zapier has an MCP Client app, currently in beta, that connects to a remote MCP server over Streamable HTTP with OAuth. Add SpendixAI as a connection and sign in once.
Connect in a few minutes.
In Zapier, SpendixAI is added as a connection to the MCP Client app.
Copy the server address
In SpendixAI open Developer → MCP connections and copy the MCP server URL.
Add the connection
In Zapier open the Apps page and choose + Add connection. Search for MCP Client and choose Add connection.
Fill in Connect an Account
Paste the server address into Server URL, set Transport to Streamable HTTP and set OAuth to Yes. Then choose Yes, Continue to MCP Client.
Sign in and approve
Log in to SpendixAI and grant access. Choose your workspace and a permission preset. Read only is recommended to begin.
Rename the connection
Rename it to something like spendixai so you can find it when you build a Zap.
https://spendix-api.kriva.studio/mcpThe form also has an optional Bearer Token field. Zapier ignores it when OAuth is set to Yes, so SpendixAI does not use it.
What you need
- A Zapier account with access to the MCP Client app, which is in beta
- A SpendixAI workspace
- The server address from Developer → MCP connections
Good to know
- Zapier describes the MCP Client as in active development and subject to change, so screens may differ from the steps above.
- Which Zapier plans include the MCP Client was not confirmed in the documentation we read.
- No approval prompt is described. Zaps run automatically, so keep the SpendixAI connection Read only and add your own approval step if a Zap could ever write data.
- The Zapier MCP Client supports tool calls only, according to its help article.
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.
Zapier MCP Client and SpendixAI.
Does the connection need an API key?
No. With OAuth set to Yes, Zapier signs in through the SpendixAI consent screen and the optional bearer token is ignored.
Can a Zap add expenses by itself?
Only if you grant a preset that allows writes. Read only lets a Zap look at records and reports but not change 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 Zapier’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 Zapier MCP Client into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.


