AI and MCP

How to connect Make to SpendixAI with MCP

Add SpendixAI to a Make scenario using the MCP Client app, authenticate once, and keep the automation read-only. Includes what the open beta leaves unconfirmed.

Editorial illustration for How to connect Make to SpendixAI with MCP

Make, the automation platform that used to be called Integromat, now has an MCP Client app. It lets a scenario call tools on a remote MCP server. This article shows how to point it at SpendixAI, a personal expense tracker for India that we build, so a scenario can read your spending records.

The short version

You add a module from the MCP Client app, create a connection that holds the server address, and authenticate on SpendixAI's own sign-in page. There is no API key. We checked the steps against Make's documentation in November 2026, though the feature is an open beta and Make says functionality and pricing may change.

Walk through the connection

  1. In SpendixAI open Developer → MCP connections and copy the server address.
  2. In a Make scenario add a module from the MCP Client app. The documentation names Call a tool and Execute an action with AI.
  3. Choose Create a connection.
  4. Give it a Connection name, for example spendixai.
  5. For MCP Server choose + New MCP Server.
  6. In the URL field type <your SpendixAI server address>.
  7. Leave the API key and access token empty. Make asks for them only if a server needs one, and SpendixAI does not.
  8. Choose Save, then authenticate when prompted. Pick your workspace and choose Read only.

After you save, Make may ask you to authenticate and confirm access. That sends you to SpendixAI, where you sign in, choose the workspace and select one of three presets. Read only lets the scenario view transactions and reports. Read and add can also create transactions and upload documents. Full access adds categorisation rules and insights. Billing and member settings are never exposed to an assistant.

What we could not confirm

QuestionStatus
Which plans include the MCP ClientNot confirmed in the documentation we read
Transport used (Streamable HTTP or SSE)Not confirmed in the documentation we read
Approval before a tool runsNone described; scenarios run on their own
Fixed redirect addressMake documents one for the app; SpendixAI registers clients itself, so it should not be needed
Beta stabilityMake calls it an open beta

Scenarios worth trying

Use Call a tool when you know which SpendixAI tool you want, or Execute an action with AI when you would rather describe the goal. A scenario that asks what you spent on food last month compared with the month before is a good first test. After that, try a list of the merchants you paid most often this quarter, or your recurring charges with what each costs per year.

Any wording in the result comes from the AI model you connect, under that provider's terms. Compare important figures against the matching SpendixAI report, and do not treat estimated GST or tax numbers as advice; a chartered accountant can confirm them.

Habits that keep a scenario safe

  • Run the scenario once manually and read the output before you set a schedule.
  • Name the connection clearly, so a second person can tell what it reaches.
  • Keep one scenario for reading and, if you ever need writes, a separate one with its own approval step.
  • Re-check the connection after Make updates the app, since the beta can change.

These are ordinary good practice rather than anything Make requires, but they cost little and they matter more when the data is your own spending.

Turning it off

Disconnect the assistant from Developer → MCP connections in SpendixAI whenever you like. Because SpendixAI re-checks the member's role on each call, a person who loses workspace access loses the connection too. If a Make menu differs from the one described here, follow Make's current guide.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports