What this setup gives you
Zapier's MCP Client lets a Zap call tools on an outside MCP server. Point it at SpendixAI and a Zap can read your expense records and reports. The feature is a beta, so expect the screens to shift, and read the caveats section before you build anything you depend on.
Before you start
- A Zapier account that can see the MCP Client app. Which plans include it was not confirmed in the documentation we read.
- A SpendixAI workspace. SpendixAI is our own product: an expense tracker for India that reads uploaded statements and manual entries, and never asks for net-banking logins.
- The SpendixAI server address from Developer → MCP connections, copied with the copy button.
Step by step
- In Zapier open the Apps page and choose + Add connection.
- Search for MCP Client and choose Add connection.
- On the Connect an Account form, enter <your SpendixAI server address> in the Server URL field.
- Set Transport to Streamable HTTP.
- Set OAuth to Yes, then choose Yes, Continue to MCP Client.
- Log in to SpendixAI when the page opens, pick your workspace and select Read only.
- Rename the new connection to spendixai so it is easy to find inside a Zap.
The form also shows an optional Bearer Token field. Zapier ignores it when OAuth is set to Yes, and SpendixAI does not need one, so leave it alone.
Caveats in one place
| Point | Why it matters |
|---|---|
| Beta status | Zapier says the app is in active development and may change |
| Plan requirement | Not confirmed in the documentation we read |
| Tool calls only | The MCP Client uses tools; it does not cover other MCP features |
| No approval prompt | Zaps run automatically, so nothing pauses to ask you |
| Scope you choose | Read only on SpendixAI keeps every Zap to viewing |
Why the approval gap matters
A chat app can stop and ask before it touches your data. A Zap cannot. It runs when its trigger fires, whether you are looking or not. That is why the permission preset you pick on the SpendixAI consent screen carries more weight here than anywhere else. With Read only, the worst a misconfigured Zap can do is read figures. With Read and add, it could create expenses on a schedule. If you ever widen access, build a human approval step into the Zap itself.
SpendixAI also limits an assistant to what the signed-in person's workspace role allows, checks that on every call, and keeps billing and member settings out of reach entirely.
Ideas that fit a read-only Zap
- A monthly summary email asking what you spent on food last month compared with the month before.
- A quarterly note on which merchants you paid most often.
- A yearly list of recurring charges with what each costs per year.
The wording of any summary comes from the AI step you add, under its own provider's terms. Check key figures in the matching SpendixAI report, and leave tax figures for a chartered accountant to confirm.
A cautious first test
Before you trust a Zap with a schedule, run it once by hand. Open the test run, read what the MCP Client step returned, and compare one or two numbers with the same period in SpendixAI. If the figures match, switch the Zap on. If they do not, the usual cause is a different date range or a different workspace chosen on the consent screen, so check both before blaming the connection.
It also helps to start with a single step. One MCP Client action followed by one email is easy to read and easy to switch off. Add filters, formatting and AI summaries only after that basic path behaves, and keep a note of which connection each Zap uses so you know what to disconnect later.
Checking and disconnecting
We checked these steps against Zapier's documentation in November 2026. If your screen differs, follow Zapier's current guide. To cut access at any point, go to Developer → MCP connections in SpendixAI, where connected assistants are listed and can be disconnected.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


