How to connect an AI assistant to SavingStat

Before you start

To connect an AI assistant to SavingStat you need an account you can sign in to and an assistant that supports connecting to outside services. Nothing is installed and nothing runs on your computer.

Every assistant asks you to sign in to SavingStat and approve access once. On that screen you choose what the connection may do: read only, so it answers questions without changing anything, or read and change. Read what an AI assistant can see and change before you allow changes.

The wording of the menus below moves around between versions. Look for the section about connectors, integrations or outside tools, and for the option to add one of your own by address.

SavingStat is not in any assistant's built-in list of connectors, so searching that list will not find it. You add it yourself by address, using whatever the assistant calls a custom connector. The next section is everything you have to type.

What to type in

Assistants word this differently, but they all ask for the same two things: a name and an address. Only the address has a label that moves around. It may be called the server URL, the remote MCP server URL, or just the URL.

The name is yours to choose, and nothing breaks if you pick something else; it only labels the connection in the assistant's own list. The address is fixed, and it is the part that has to be exactly right. Here are both, with a button on each that copies it.

Copy the address rather than retyping it. It starts with https, it is api.savingstat.com and not the savingstat.com you sign in at, and it ends at /mcp with nothing after it.

Some assistants also offer a client ID and a client secret, usually tucked away under advanced or optional settings. Leave both empty. SavingStat hands those to the assistant by itself the first time it connects, so there is no key for you to generate and nothing to copy out of your account.

Claude

Open Claude's settings, go to Connectors, and scroll past the ready-made ones to the button that adds a custom connector. Claude asks for a name and a remote MCP server URL. Put SavingStat in the first, paste the address above into the second, and leave the advanced OAuth fields empty.

Claude adds the connector and then asks you to connect it, which opens a SavingStat page in your browser. Sign in if you are not already, check what is being asked for, and approve it. Claude shows the connector as connected when it is done.

Custom connectors work on every Claude plan, including the free one, though a free account can hold only one at a time. On Team and Enterprise an owner adds the connector for the organisation first, and everyone else then connects their own account to it. Claude's own instructions are at Get started with custom connectors.

Ask it something to check. "What is my current balance?" should come back with a real figure.

ChatGPT

Read this part before you start. ChatGPT keeps custom connectors behind developer mode, which is a paid-plan feature, so a free account cannot add one. On individual Plus and Pro accounts a custom connector can only read: SavingStat will answer your questions there but will never record anything, whatever you approved on the consent screen. Recording needs a Business, Enterprise or Edu workspace. If you want an assistant that keeps your records rather than only reading them, Claude is the simpler route.

If your plan supports it, turn developer mode on in settings, under the connector or workspace permissions. Then add a connector: name it SavingStat, paste the address above into the MCP server URL field, and choose OAuth as the authentication if it asks. A description is optional and is only a note to yourself.

Approve access on the SavingStat page that opens, then ask "how much did I spend this month?" to confirm it is working.

OpenAI changes this often, so check Developer mode and MCP apps in ChatGPT if what you see does not match.

Gemini

Gemini connects to outside services through the Gemini CLI rather than through the Gemini website. Install the CLI, then add SavingStat to its settings file at ~/.gemini/settings.json, where savingstat is the name and httpUrl is the address:

{
  "mcpServers": {
    "savingstat": {
      "httpUrl": "https://api.savingstat.com/mcp"
    }
  }
}

Start the CLI again. It works out on its own that SavingStat needs you to sign in, and opens the page for you to approve access. If it does not, run /mcp auth and pick savingstat, which starts the same thing by hand.

The CLI's own reference is at MCP servers with the Gemini CLI.

If you use the Gemini website rather than the CLI, there is no way to add SavingStat to it at the moment.

LM Studio

LM Studio runs a model on your own computer and can still connect to SavingStat over the internet.

Open its integrations settings and edit mcp.json, then add SavingStat alongside anything already there, with savingstat as the name and the address under url:

{
  "mcpServers": {
    "savingstat": {
      "url": "https://api.savingstat.com/mcp"
    }
  }
}

Save the file. LM Studio opens a SavingStat page to sign in and approve access. Its own notes are at Model Context Protocol in LM Studio.

Two things are worth knowing here. Use a model that supports tools, or SavingStat will be connected but never called. And leave LM Studio's own confirmation prompt switched on, because a model running on your computer is less predictable about pausing for you than a hosted assistant is.

Checking that the connection works

Ask the assistant what your current balance is, and compare the answer with the figure on your dashboard. They should match. Exactly.

If they do, ask it something only your own records could answer, such as what you spent on groceries last month. A connected assistant reads your real transactions rather than guessing.

When the connection does not work

You cannot find SavingStat in the assistant's list of connectors. SavingStat is not in those lists. Look for the option to add a connector of your own by address instead, and give it the name and address from the top of this guide.

The assistant says the address is invalid, or that it cannot reach the server. Compare what you pasted against the address above, character by character. Dropping the s from https, leaving a slash after /mcp, or using savingstat.com in place of api.savingstat.com each fail this way.

The assistant says it has no SavingStat tools. The connection did not finish. Approving access is the step easiest to miss: watch for the SavingStat page opening in your browser, and sign in if it asks. Remove the connection and add it again.

It keeps asking you to authenticate, and no approval page ever appears. The assistant is holding on to an old connection that no longer exists on SavingStat's side, which is what happens after you disconnect it from your SavingStat settings. Remove it from the assistant and add it again, so it starts a fresh connection rather than retrying the old one.

It answers questions but says it cannot change anything. You approved reading only. That is a reasonable setting to stay on. If you want it recording things for you, disconnect and connect again, approving changes this time.

Its answers are missing recent spending. Transactions from an import stay as drafts until they are reviewed, and drafts are left out of totals on purpose. Publish the ones that are right, and ask again.

A figure looks wrong. Ask which transactions it used. It can list them, and comparing that list against the same period on your dashboard usually shows whether the gap is a draft, a different date range, or a different currency.

Nothing appears in Gemini. The Gemini website cannot add a connection of its own; it has to be the Gemini CLI. See the Gemini section above.

You want it to stop. Disconnect it in your SavingStat settings. That works even if you no longer have access to the assistant itself.