Kilo Code lives inside VS Code, so the natural place to ask about your spending is the same side panel where you already talk to the agent. Because it supports remote MCP servers with OAuth 2.0, you do not copy any key from one place to another. You add an address, sign in once and decide what the agent may do.
The data comes from SpendixAI, our own app for tracking expenses in India. It is built around uploaded bank and card statements and entries you type in yourself, and it never asks for net-banking details.
Where Kilo Code fits
Kilo Code is available as a VS Code extension and as a command-line tool, and each has its own setup tab in its documentation. This guide follows the extension. It tries Streamable HTTP first and falls back to SSE, which its documentation marks as deprecated, so you do not need to choose a transport.
Two ways to add the server
- Copy the server address from Developer → MCP connections in SpendixAI.
- In VS Code open Kilo Code's Settings, then MCP, then Add Server, and choose Remote (HTTP).
- Paste the address and save. The sidebar route is Settings, Agent Behaviour, MCP Servers.
- Wait for the server status to change to needs_auth.
- Use the notification in VS Code to start the sign-in.
If you prefer a file, the top-level key is mcp. Under it, add spendixai with the type set to remote, the url set to <your SpendixAI server address> and enabled set to true. The global file is ~/.config/kilo/kilo.jsonc, or kilo.json. A project file named kilo.jsonc, or one at .kilo/kilo.jsonc, wins over the global one.
Signing in from VS Code
The browser opens on SpendixAI's consent screen. Sign in, choose the workspace and tick one preset. We suggest the read-only one, which allows viewing transactions and reports and nothing else. The other two add creating transactions and uploading documents, then categorisation rules and insights. Billing stays out of reach of every assistant.
Permission rules and Approve Always
Kilo Code treats MCP tools like its other tools. Each one is named with the server first, for example spendixai followed by an underscore and the tool name, and by default the agent asks before using it. The Permission Dock offers Approve Always, which saves a lasting allow rule. A manual rule such as spendixai with a star at the end, set to allow, does the same for every tool. Avoid both while you are learning what the agent does with your records.
The documentation also mentions an older alwaysAllow setting in the legacy mcpServers format. If you copy an old example from a forum, remove that line.
Requirements and caveats
| Area | What to know |
|---|---|
| Installed software | The Kilo Code extension or CLI |
| SpendixAI side | A workspace and its server address |
| CLI sign-in | A command for it was not documented on the page we read |
| Plan or minimum version | Not stated in the documentation we read |
| Turning OAuth off | Possible in Kilo Code, but SpendixAI needs it, so leave it on |
Switching the connection off
There are two places to cut access. In Kilo Code you can set the server's enabled value to false, which stops the extension from using it. In SpendixAI, the page under Developer → MCP connections lists connected assistants and lets you disconnect any of them. The second is the stronger option, because it removes the permission rather than the shortcut to it.
Remember too that the presets sit on top of your own workspace role. A member with limited rights cannot hand more power to an assistant than they hold, and that is checked on each call.
Setup was checked against Kilo Code's documentation in November 2026. Menus and file names change, so follow the current guide if yours differ. A sensible first test is asking which merchants you paid most often this quarter, then comparing the top few with the matching SpendixAI report.
Useful ideas start with a clearer picture of your own spending.
Explore your reports


