Amp + SpendixAI
Amp can keep a remote MCP definition with your account so it works in every Amp client. Add SpendixAI with OAuth, log in once, and set a per-tool policy.
Connect in a few minutes.
Amp adds SpendixAI as a personal remote MCP definition and signs in through your browser.
Copy the server address
In SpendixAI open Developer → MCP connections and copy the SpendixAI server address.
Add a remote definition
Run the first command below. It stores SpendixAI for your personal scope with OAuth as the sign-in method.
Log in
Run the second command. Amp opens a browser sign-in. Sign in to SpendixAI, choose your workspace and pick a permission preset. Read only is the recommended start.
Set a tool policy
In the MCP server settings of your Amp account, set each SpendixAI tool to Ask First. The default policy is Allow, which runs tools without asking.
amp mcp remote --personal add spendixai https://spendix-api.kriva.studio/mcp --auth oauth
amp mcp remote --personal login spendixaiOther scopes are --workspace, --project and --current-project. A local alternative in settings.json is "amp.mcpServers": { "spendixai": { "url": "https://spendix-api.kriva.studio/mcp" } }, or the command amp mcp add spendixai https://spendix-api.kriva.studio/mcp.
What you need
- Amp installed and an Amp account
- A SpendixAI workspace
- The SpendixAI server address from Developer → MCP connections
- A browser for the sign-in step
Good to know
- Amp’s default policy for remote MCP tools is Allow, including for tools added later. Change it to Ask First, or Disabled, before you connect finance data.
- Ask First means the account owner approves each call, and subagents cannot call such tools.
- Remote definitions are stored with your Amp account, and Amp’s own servers connect to the MCP server.
- The documentation we read did not state a minimum plan or 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.
Amp and SpendixAI.
Should I use the remote definition or the local settings file?
Amp’s documentation describes both. A remote definition is stored with your account and works across Amp clients, while a settings.json entry lives in local configuration. This guide uses the remote definition.
How do I stop Amp using SpendixAI?
Set the tools to Disabled in your Amp MCP server settings, and revoke the connection in SpendixAI under Developer → MCP connections.
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 Amp’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 Amp into your finances.
Create your SpendixAI workspace, import a statement, then connect the assistant.