Why Crush is different
Most assistants on our MCP pages are set up through a menu. Crush, the terminal agent from Charm, is set up through a small entry in a config file. That is quick, but it asks for a little more care, which is why this guide spends time on the caveats.
The entry itself
The entry is named spendixai, has the type http, carries <your SpendixAI server address> as its url, and sets oauth to true. With oauth switched on and no client ID, Crush tries dynamic client registration, which SpendixAI supports. So there is no client ID or secret to fill in.
Steps
- Copy the server address from Developer → MCP connections in SpendixAI, our own product.
- Open the folder you will run Crush in and read any existing Crush config there first.
- Add the entry described above to your Crush configuration.
- Start Crush. With oauth on, it uses its built-in authorization-code flow to sign in; when the browser step begins was not confirmed.
- On the SpendixAI screen, choose your workspace and a preset. Read only is the sensible start.
Two warnings from Charm
Charm's README says Crush's config files, both crush.json and crushrc, are trusted code that runs when loaded. So a config file in a folder you downloaded deserves a read before you launch Crush there. The README also calls the older JSON config format still supported but deprecated.
Tool names and approvals
Crush names MCP tools with the prefix mcp_ and then the server name, so SpendixAI's tools appear as mcp_spendixai_ followed by the tool name. By default Crush prompts before using a tool. A permissions allow command skips the prompt for tools you list, and a deny command hides them. There is also a --yolo flag that skips approvals, which we advise against for expense records.
Summary table
| Point | Detail |
|---|---|
| Type | http |
| OAuth | oauth set to true; dynamic registration when no client ID is given |
| Config file for the JSON snippet | Not confirmed |
| Browser sign-in trigger | Not confirmed |
| Version or plan | None stated; open source |
| Disconnect | Remove the entry, then Developer → MCP connections |
Choosing the SpendixAI preset
The consent screen offers Read only, Read and add and Full access. Read only means Crush can 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 offered, and your workspace role limits every assistant, with access re-checked on each call.
A note on keeping prompts on
Crush's permission commands are handy for code, where you may happily allow a tool again and again. For expense data we would leave prompts on, so you see each tool before it runs. If you ever allow a tool permanently, do it only for tools that merely read, and review the list now and then.
What to ask once it works
Pick questions whose answers you can verify yourself. You might ask what you spent on food last month compared with the month before, which merchants you paid most often this quarter, or which recurring charges you have and what each costs per year. Crush answers from the records in your SpendixAI workspace, which come from statements you uploaded and expenses you typed in. There is no bank connection and no SMS reading behind it.
A quick first test
Ask Crush which merchants you paid most often this quarter, then compare the top name with the SpendixAI report for merchants. If they match, the connection is working as intended. If Crush cannot see any tools, check your config and the sign-in step before suspecting SpendixAI.
We checked this against Charm's documentation in November 2026. Because the page we relied on is a README, details may move faster than a formal docs site.
Useful ideas start with a clearer picture of your own spending.
Explore your reports

