Kimi Code CLI + SpendixAI
Kimi Code CLI reads MCP servers from a JSON file and can sign in to remote ones through your browser. Add the server address, log in once and the terminal agent can query your records.
Connect in a few minutes.
Kimi Code CLI is set up through /mcp-config or an mcp.json file, followed by a login command.
Copy the server address
In SpendixAI open Developer → MCP connections and copy the MCP server URL.
Add the server
Run /mcp-config in the Kimi Code CLI screen to add an entry, or edit the mcp.json file directly with the snippet below.
Log in
Run /mcp-config login spendixai. Your browser opens so you can authorise the connection.
Approve access in SpendixAI
On the SpendixAI consent screen sign in, choose your workspace and pick a permission preset. Start with Read only.
Ask a question
Back in the terminal, ask about your spending. Tools appear to the agent as mcp__spendixai__ followed by the tool name.
{ "mcpServers": { "spendixai": { "url": "https://spendix-api.kriva.studio/mcp" } } }The user file is ~/.kimi-code/mcp.json, or mcp.json under the folder named by KIMI_CODE_HOME. A project file at .kimi-code/mcp.json overrides it, so keep a personal finance server in the user file.
What you need
- Kimi Code CLI installed
- A SpendixAI workspace
- A browser on the same machine for the sign-in step
Good to know
- The documentation we read did not state a minimum version or plan.
- A kimi mcp add command with an HTTP transport option appeared in secondary results but was not on the vendor page we read, so we have not used it.
- Calls that match no permission rule prompt you. Approve for this session allows later calls of that kind, and permanent rules go in config.toml under permission rules with a decision and a pattern.
- In Ask When Needed mode, MCP calls are approved automatically, so for finance data set explicit rules and keep SpendixAI on Read only. The Kimi chat app itself has no documented way to add your own remote MCP server.
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.
Kimi Code CLI and SpendixAI.
Does this work in the Kimi chat app?
Not as far as the documentation we read shows. It describes adding remote servers in Kimi Code CLI, not in the chat app.
How do I stop it asking or auto-approving?
Use permission rules in config.toml. For a finance server, write explicit rules for the tools you accept instead of relying on a mode that approves MCP calls for you.
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 Moonshot AI’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 Kimi Code CLI into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.
