AI and MCP

How to connect Cursor to SpendixAI with MCP

Connect Cursor to SpendixAI with a short mcp.json entry. Cursor handles OAuth sign-in itself, so no API key is needed. Includes approval behaviour and starter questions.

Editorial illustration for How to connect Cursor to SpendixAI with MCP

Cursor needs one small JSON entry and nothing else. There is no key to paste, because when the entry has no headers Cursor starts an OAuth sign-in on its own the first time it connects.

Before editing anything

SpendixAI is built by us, and we wrote these steps from Cursor's MCP documentation as it stood in November 2026. Cursor changes quickly, so menus may have moved by the time you read this. You need the server address from Developer → MCP connections in SpendixAI, and a SpendixAI sign-in through Google. The Cursor page we read states no plan or version requirement.

Choose a file

Cursor reads server entries from .cursor/mcp.json inside a project, or from mcp.json in the .cursor folder of your home directory for every project. For a connection to personal finance data, the home-folder file avoids tying SpendixAI to a codebase that colleagues may open.

The entry

In the file, add an mcpServers object. Inside it, create an entry named spendixai with a single field, url, holding <your SpendixAI server address>. Leave out headers. Cursor's documentation says it uses the authorization code flow with PKCE, reads the server's protected resource metadata and registers itself as a public client. That matches SpendixAI, which supports dynamic client registration, so no pre-registration is needed.

  1. Copy the address from Developer → MCP connections.
  2. Open or create mcp.json in your chosen location.
  3. Add the spendixai entry with the url field, then save.
  4. Return to Cursor. The first connection attempt starts the sign-in, and a SpendixAI consent screen opens in your browser.
  5. Sign in, choose the workspace, select Read only and approve.

Approvals in Cursor

By default Cursor asks for approval before it uses an MCP tool. Its Auto-review run mode behaves differently: tools you have put on an allowlist run immediately. For SpendixAI, keep any allowlist short. Reading a summary is low risk, but a tool that adds or changes records should never run without you seeing it.

The consent screen sets the outer limit. Read only is the recommended preset and covers transactions and reports. Read and add also creates transactions and uploads documents. Full access adds categorisation rules and insights. Billing and member settings are never exposed, and an assistant can never exceed the role of the person who signed in.

ItemDetail
Project file.cursor/mcp.json
Global filemcp.json in the .cursor folder of your home directory
Sign-inOAuth with PKCE; refresh tokens are used
Static client optionExists in Cursor, not needed for SpendixAI
Approval defaultCursor asks before using MCP tools
Plan or version requirementNot stated on the page we read

Questions worth asking first

  • What did I spend on subscriptions last month?
  • Give me a weekly spending total for the past eight weeks.
  • Which transactions have no category yet?
  • Which merchant had the biggest single charge this quarter?

Because Cursor is a coding tool, it is easy to forget that this chat can also see your money data. Keep spending questions in a separate conversation from code work, and double-check any figure that feeds a tax or accounting decision against the SpendixAI report.

A practical habit: after the first sign-in, ask a question you already know the answer to, such as last month's total, and compare it with the SpendixAI dashboard. If the two agree, you have a working baseline and can trust the connection a little more. If they differ, stop and find out why before asking anything else.

Limits of what we confirmed

Cursor's documentation mentions a fixed-credential option and some redirect addresses for that case, which we left out because SpendixAI does not need them. We could not confirm a one-click install link format for Cursor, so the file route above is the one we recommend. To end access, use the disconnect option on the Developer → MCP connections page, which lists every connected assistant.

SPENDIXAI JOURNAL

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

Explore your reports