Coding agent · Charm

Crush + SpendixAI

Crush can talk to remote MCP servers over HTTP and has a built-in OAuth flow. You add a short entry marked for OAuth, and Crush uses dynamic client registration to introduce itself to SpendixAI.

Crush installedA SpendixAI workspaceA browser on the same machine for the sign-in step
What did I spend on food last month compared with the month before?
Crush · using SpendixAI · illustrativeIt looks at the records you allowed and answers from them. You stay in control of what is shared.
Read only to start · You approve what is shared

Connect in a few minutes.

Crush is configured with a small JSON entry that sets the type to http and turns OAuth on.

Copy the server address

In SpendixAI open Developer → MCP connections and copy the MCP server URL.

Add the entry

Add the snippet below to your Crush configuration, replacing the placeholder with the address you copied. Review the file first, because Crush treats its config files as trusted code.

Start Crush

Open Crush. With oauth set to true it uses its built-in authorization-code flow to sign in to SpendixAI.

Approve access

On the SpendixAI consent screen sign in, choose your workspace and pick a permission preset. Start with Read only.

Crush config entry
{
  "mcp": {
    "spendixai": {
      "type": "http",
      "url": "https://spendix-api.kriva.studio/mcp",
      "oauth": true
    }
  }
}

Crush also reads a crushrc file at ./.crushrc, ./crushrc or ~/.config/crush/crushrc (on Windows, %USERPROFILE%\.config\crush\crushrc), where an mcp add command can add a server with static headers.

What you need

  • Crush installed
  • A SpendixAI workspace
  • A browser on the same machine for the sign-in step

Good to know

  • The README calls the JSON config format still supported but deprecated, and it does not say which file this JSON snippet belongs in. Check Charm’s current guide for the right file.
  • How and when the browser sign-in starts, and how to switch OAuth on from a crushrc file, were not confirmed in the documentation we read.
  • MCP tools appear to Crush as mcp_spendixai_ followed by the tool name. Permission rules can allow a tool without prompting or hide it; leave prompts on for a finance server.
  • Crush has a --yolo flag that skips approvals. We do not recommend it with your expense records. The documentation named no minimum version or plan.

Questions to start with.

These need only read access. Add records or upload statements once you have moved to a broader preset.

“What did I spend on food last month compared with the month before?”“Which merchants did I pay most often this quarter?”“List my recurring charges and what each costs per year.”

Start read only. Widen it later.

Read onlyRecommended

Ask about transactions, summaries and reports. Nothing can be added, changed or uploaded.

Read and add

Ask questions, add expenses and upload statements or receipts.

Full access

Everything above, plus categorisation rules and insights. Billing and member settings stay in the console.

Crush and SpendixAI.

Why must I review the config first?

Charm warns that Crush config files run as trusted code when loaded, so open any config from an unfamiliar folder and read it before you start Crush there.

Do I need a client ID?

Not for SpendixAI. Without a client ID Crush tries dynamic client registration, which SpendixAI supports.

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 Charm’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.

Using something else?

More assistants that can connect to SpendixAI. See all 42.

Bring Crush into your finances.

Create your SpendixAI workspace, import a statement, then connect the assistant.