Kiro + SpendixAI
Kiro supports remote MCP servers that need OAuth and handles the browser sign-in itself. You add SpendixAI to a JSON config file and approve access once.
Connect in a few minutes.
In Kiro, MCP support is switched on in settings and SpendixAI is added to the MCP config file.
Copy the server address
In SpendixAI open Developer → MCP connections and copy the SpendixAI server address.
Turn on MCP
Open Settings with Ctrl or Cmd plus comma, search for MCP and enable the MCP support setting.
Open the config and add SpendixAI
In the Command Palette run Kiro: Open user MCP config (JSON), then add the entry below with the server address in the url field.
Save and sign in
Save the file. Kiro reconnects and opens a browser sign-in. Sign in to SpendixAI, choose your workspace and pick a permission preset. Read only is the recommended start.
Keep tool prompts on
Kiro asks before it runs a tool by default. Leave SpendixAI off the autoApprove list so each call still needs your approval.
{
"mcpServers": {
"spendixai": {
"url": "https://spendix-api.kriva.studio/mcp"
}
}
}A workspace file at .kiro/settings/mcp.json overrides the user file. In Kiro CLI, /mcp auth, /mcp cancel-auth and /mcp logout manage the sign-in.
What you need
- The Kiro IDE (or Kiro CLI, which is the renamed Amazon Q Developer CLI)
- A SpendixAI workspace
- The SpendixAI server address from Developer → MCP connections
- A browser for the sign-in step
Good to know
- Kiro’s documentation says tools can be listed under autoApprove so they run without asking, and that you should review them first. Do not use the wildcard for SpendixAI.
- If SpendixAI does not register a client automatically, Kiro falls back to a default client setup. The authorization server’s issuer must match exactly or discovery stops.
- Kiro CLI 3.2.0 or later is documented for sign-in without an oauth block in the config. Subscription tiers were not confirmed in the documentation we read.
- The exact flags for adding a server with the kiro-cli mcp add command were not confirmed. Use the JSON file.
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.
Kiro and SpendixAI.
Which config file should I use?
The user file applies in every workspace. A workspace file applies to one project and overrides the user file. For personal finance data the user file is the safer choice.
Do I need to paste a client ID or secret?
No. The IDE uses public clients with no secret, and SpendixAI handles registration through its sign-in flow.
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 Amazon Web Services’ 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 Kiro into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.