Kilo Code + SpendixAI
Kilo Code supports remote MCP servers with OAuth 2.0. Add SpendixAI from the MCP settings or a config file, sign in once, and ask about your spending from the agent.
Connect in a few minutes.
In Kilo Code, SpendixAI is added as a remote (HTTP) server, either in settings or in a config file.
Copy the server address
In SpendixAI open Developer → MCP connections and copy the SpendixAI server address.
Add a remote server
In the VS Code extension open Settings → MCP → Add Server → Remote (HTTP) and paste the server address. Or add the config entry below.
Sign in
When the server needs sign-in, Kilo Code shows a needs_auth notification in VS Code that starts the sign-in. Choose your workspace in SpendixAI and pick a permission preset. Read only is the recommended start.
Keep the default permissions
Kilo Code asks by default. Avoid Approve Always for SpendixAI tools, which saves a permanent allow rule.
{
"mcp": {
"spendixai": {
"type": "remote",
"url": "https://spendix-api.kriva.studio/mcp",
"enabled": true
}
}
}The global file is ~/.config/kilo/kilo.jsonc (or kilo.json). A project file, kilo.jsonc or .kilo/kilo.jsonc, takes priority. Tool names appear as spendixai_ followed by the tool name.
What you need
- Kilo Code installed (VS Code extension or CLI)
- A SpendixAI workspace
- The SpendixAI server address from Developer → MCP connections
- A browser for the sign-in step
Good to know
- Kilo Code tries Streamable HTTP first and falls back to SSE, which its documentation marks as deprecated.
- A command-line sign-in command for the CLI was not documented on the page we read. In VS Code the notification starts the sign-in.
- Approve Always in the Permission Dock saves an allow rule, and a rule such as spendixai_* set to allow removes the prompts. Do not set that for finance data.
- The documentation also mentions an older alwaysAllow setting in the legacy mcpServers format.
- The documentation we read did not state a plan or minimum version.
Questions to start with.
These need only read access. Add records or upload statements once you have moved to a broader preset.
Start read only. Widen it later.
Ask about transactions, summaries and reports. Nothing can be added, changed or uploaded.
Ask questions, add expenses and upload statements or receipts.
Everything above, plus categorisation rules and insights. Billing and member settings stay in the console.
Kilo Code and SpendixAI.
Can I turn off the OAuth sign-in?
Kilo Code allows oauth to be set to false, but SpendixAI needs the sign-in, so leave it on.
Where do I see the SpendixAI tools?
They appear with names that start with spendixai_. Permission rules use that same pattern.
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 Kilo Code’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.
Bring Kilo Code into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.