AI and MCP

How to connect Amp to SpendixAI with MCP

Store SpendixAI as a remote MCP definition in Amp, log in with OAuth and switch every tool to Ask First, because Amp's default is to run tools without asking.

Editorial illustration for How to connect Amp to SpendixAI with MCP

One default matters more than any other when you connect Amp to money records. For remote MCP tools, Amp's policy starts at Allow, and that includes tools added later. So the order of work here is: connect, then change the policy, then ask questions.

Why a remote definition

Amp's documentation describes two routes. A local entry in settings.json lives on one machine. A remote definition is stored with your Amp account and works across Amp clients, and Amp's own servers make the connection to the MCP server. We use the remote route here, with personal scope so that nobody else in a workspace or project sees it.

What it connects to is SpendixAI, our own product for tracking expenses in India from statements and cash entries. It has no bank link and no SMS access.

Add it and log in

  1. Copy the server address from Developer → MCP connections in SpendixAI.
  2. Run amp mcp remote with the personal flag, then add, the name spendixai, the address and an auth setting of oauth.
  3. Run amp mcp remote with the personal flag, then login and the name spendixai.
  4. Amp opens a browser sign-in. Sign in to SpendixAI.
  5. Choose your workspace and pick a permission preset on the consent screen.

Where the address goes, type <your SpendixAI server address>. Other scopes exist, namely workspace, project and current-project, but personal is the right one for private finance data. There is also a local alternative, an amp.mcpServers entry with a url, or the amp mcp add command.

Set each tool to Ask First

In the MCP server settings of your Amp account, each tool has a policy. Allow runs it without asking. Ask First makes the owner approve each call, and subagents cannot call such tools. Disabled switches it off. Choose Ask First for SpendixAI's tools, or Disabled for any you do not need.

What the presets mean for Amp

The consent screen offers Read only, Read and add, and Full access. Read only covers viewing transactions and reports. Read and add allows creating transactions and uploading documents. Full access also covers categorisation rules and insights. Pairing Read only with Ask First gives two separate safeguards, one set by SpendixAI and one by Amp. Your own role in the workspace limits things further.

Reference

SettingWhat to know
Scope usedPersonal
Sign-in methodOAuth through the browser
Default tool policyAllow, including for tools added later
Recommended policyAsk First
Plan or versionNot stated in the documentation we read
Revoking accessDisable the tools in Amp, and disconnect under Developer → MCP connections

A note on network access

Since remote definitions are used from Amp's side, a server that only accepts connections from certain addresses would need to allow Amp's. Most people will not meet this, but it explains a failed connection that works fine from your own machine. We did not find anything more specific in the documentation we read.

Disconnecting

To stop Amp using SpendixAI, set the tools to Disabled in your Amp settings. To end the permission itself, open Developer → MCP connections in SpendixAI and disconnect Amp from the list of connected assistants. Do both if you are handing over a shared computer. Neither step deletes any of your expense records, which stay in your SpendixAI workspace as before.

We checked these steps against Amp's documentation in November 2026. Commands change, so follow the current Amp guide if one fails. Once everything is set, ask which merchants you paid most often this quarter, and check any figure you plan to rely on against the matching SpendixAI report.

SPENDIXAI JOURNAL

Useful ideas start with a clearer picture of your own spending.

Explore your reports