AI and MCP

How to connect n8n to SpendixAI with MCP

Use SpendixAI as an MCP tool in n8n through an MCP OAuth2 credential, limit the workflow to read tools, and note the transport question we could not confirm.

Editorial illustration for How to connect n8n to SpendixAI with MCP

Workflow tools differ from chat apps in one important way: they run without anyone watching. That matters when the tool you hand an n8n AI agent is your personal finance data. This article walks through connecting n8n to a SpendixAI workspace over MCP in a way that keeps the agent to reading.

How the pieces fit

n8n has an MCP Client Tool node that you attach to an AI Agent, and a separate MCP Client node you can use on its own. Authentication is handled by an MCP OAuth2 credential. SpendixAI, which is our own product and tracks Indian spending from statements and manual entries, supports the sign-in method this credential expects, so there is no key to paste.

Build the connection

  1. Copy the server address from Developer → MCP connections in SpendixAI.
  2. In your n8n workflow add the MCP Client Tool sub-node to an AI Agent, or add the MCP Client node.
  3. In the endpoint field enter <your SpendixAI server address>.
  4. Set Authentication to OAuth2 and create a new MCP OAuth2 credential. Name it something like spendixai.
  5. Leave Use Dynamic Client Registration switched on. It is on by default.
  6. Use the credential's connect button, sign in on the SpendixAI consent screen, pick your workspace and choose Read only.
  7. Under Tools to Include choose Selected and tick only the read tools.

Requirements and caveats

TopicDetail
n8n sideAn instance with the AI Agent node or the MCP Client node
SpendixAI sideA workspace and its server address
CredentialMCP OAuth2 with dynamic client registration on
Fallback fieldsAuthorization URL, Access Token URL, Client ID and Client Secret, not needed for SpendixAI
Not confirmedStreamable HTTP on the tool node, the exact label of the connect button, minimum version or plan

Why read only is the right start

n8n does not describe an approval step. When a workflow fires, the agent calls its tools on its own. On the SpendixAI consent screen you can choose Read only, Read and add, or Full access. For automation, begin with Read only, which allows viewing transactions and reports and nothing else. If you later need a workflow to add expenses, choose a wider preset on purpose and put your own approval step in front of the write.

The Tools to Include setting is the second lock. All, Selected and All Except are the options. Selected is the safest for money data, because new tools never appear in the workflow by surprise.

A workflow worth building

A simple one is a weekly check. A scheduled trigger starts an AI Agent with a prompt such as: list my recurring charges and what each costs per year. The agent answers from your records and you route the reply to your inbox. Another is a question you ask on demand: which merchants did I pay most often this quarter. For a monthly comparison, ask what you spent on food last month compared with the month before.

Remember that the agent's wording comes from whichever AI model you attached, under that provider's terms. Verify important numbers in the matching SpendixAI report before acting on them, and take tax questions to a chartered accountant.

Testing safely

Build the smallest possible workflow first: a manual trigger, one AI Agent and the MCP Client Tool node with a single read tool selected. Run it and ask one question. Compare the answer with the same figure in SpendixAI. Only after that should you add schedules, branches or notifications.

If the node cannot reach the server, the transport question above is the first suspect, followed by the credential. Re-run the credential's connect step and confirm that the SpendixAI consent screen appears, because a connection that never reached that screen was never authorised.

Ending access

Setup was checked against n8n's own documentation in November 2026. If a label differs on your version, follow n8n's current guide. You can disconnect the assistant at any time from Developer → MCP connections in SpendixAI, and a demoted workspace member loses access automatically.

SPENDIXAI JOURNAL

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

Explore your reports