Connect an AI Assistant

NetFiscus runs a remote MCP server. MCP (Model Context Protocol) is an open standard that lets an AI assistant talk to an application. Connect your assistant once, and you can ask about your assets, debts and returns in plain language.

You connect with your own account. The assistant reads your data and nothing else. You choose whether it can also record and correct your entries, and you can disconnect it at any time.

What you can do

• Ask questions in plain language. Balances, returns, profit and loss, projections.
• Record from chat. Give the assistant a balance, a deposit or a withdrawal with its date, and it records it.
• Correct a mistake. Ask it to fix or remove an entry you already recorded. It shows you the record first and waits for your yes.
• Update from a file or a screenshot. Paste a screenshot of your broker page, or drop in a CSV, and ask the assistant to record the balances.
• Stay in control. Reading costs nothing. Recording costs credits, exactly as it does in the app.

Prompts that work once you are connected:

• "List my assets with their latest balances."
• "How did my investments perform over the last 12 months?"
• "Show the monthly profit and loss of my Investments collection this year."
• "Which of my assets have not been updated this month?"
• "Add today's balance of 5,700.25 EUR to my Coinbase account."
• "I deposited 1,000 EUR into my Degiro account yesterday."
• "The balance I entered for Coinbase last Friday is wrong. It should be 5,650."
• "Here is a screenshot of my broker account. Record these as today's balances, but check first which ones already have a value for today."
• "Project my net worth for the long term at a 5 percent return. When do I reach financial independence?"

Updating from a file or a screenshot

Most assistants read images and files. That turns a monthly update into one message: paste a screenshot of an account summary, or attach a CSV your broker exported, and ask the assistant to record the balances.

Your assistant does the reading. It parses the picture or the file on its side, then sends us one balance at a time. We never receive the file itself, only the finished numbers.

Two things to get right:

• Ask it to check the dates first. Adding a balance always creates a new record and never replaces one. Without a check you can end up with two records for the same day. If that happens, ask the assistant to correct one of them. A correction is free.
• Each new entry costs credits, the same as entering it by hand, so a long file costs proportionally more. Reading, checking and correcting are free.

Deposits and withdrawals work the same way. For a large backlog, the app's CSV import is still faster, because it takes the whole file in one step.

Correcting and removing entries

An assistant can fix an entry you got wrong, and remove one you no longer want. This works for balances and for deposits and withdrawals.

Both actions are deliberately slow:

• The assistant reads the record first, shows you its date, amount and label, and waits for an explicit yes. One record per confirmation.
• Your tool asks as well. Claude Code, for example, asks before every removal, even when you turned other approvals off.
• A correction keeps the record and its place in your history. Only the fields you asked about change.

A correction is free. Removing a record refunds its credits: the full amount within 30 days of the day it was recorded, and half after that. Correcting a wrong number is therefore always cheaper than removing it and adding a new one.

One record can never be removed: the last remaining balance of an asset or a debt. Something has to stay.

Before you start

Every client needs the same server address:

https://app.netfiscus.com/api/mcp

Two ways to connect

Each tool supports one or both. The step-by-step sections below tell you which to use.

You create tokens under Settings, Connected apps in the app. A token is shown once, so copy it straight away. You choose Read or Read + write, you can set an expiry date, and you can revoke it at any time.

What you allow

The consent screen names exactly two permissions:

Grant read only if you just want to ask questions. See Pricing for how credits work.

Claude

Works in the Claude web app and Claude Desktop. No token needed.

1. Copy the server URL above.
2. In Claude, open the Connectors settings and add a custom connector with this URL.
3. Claude opens a NetFiscus sign-in page. Sign in and approve access.

After you approve, Claude appears under Settings, Connected apps, Authorized apps in NetFiscus.

Anthropic documents the menu path and which Claude plans allow custom connectors: Get started with custom connectors using remote MCP.

ChatGPT

ChatGPT signs in with your account and does not accept tokens.

1. In ChatGPT, turn on developer mode in the settings.
2. Add a new app or connector and paste the server URL as its connection. Include the /api/mcp path.
3. ChatGPT opens a NetFiscus sign-in page. Sign in and approve access.

OpenAI documents developer mode, the plans that include it, and the fact that it is a web feature: Developer mode.

Claude Code

Terminal tool. Both paths work.

With a token

Create a token under Settings, Connected apps, then run:

claude mcp add --transport http netfiscus https://app.netfiscus.com/api/mcp --header "Authorization: Bearer <your token>"

With sign-in

claude mcp add --transport http netfiscus https://app.netfiscus.com/api/mcp

Then start Claude Code, run /mcp, and sign in to NetFiscus in the browser that opens.

Vendor documentation: Claude Code MCP.

Codex

Works in the OpenAI Codex CLI. The Codex IDE extension shares the same configuration.

With sign-in

codex mcp add netfiscus --url https://app.netfiscus.com/api/mcp
codex mcp login netfiscus

The second command opens a browser. Sign in to NetFiscus and approve access.

With a token

export NETFISCUS_TOKEN="<your token>"
codex mcp add netfiscus --url https://app.netfiscus.com/api/mcp --bearer-token-env-var NETFISCUS_TOKEN

Vendor documentation: Codex MCP.

Cursor

Cursor reads a configuration file. Use ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside one project.

With sign-in

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

When Cursor connects, sign in to NetFiscus and approve access.

With a token

{
  "mcpServers": {
    "netfiscus": {
      "url": "https://app.netfiscus.com/api/mcp",
      "headers": {
        "Authorization": "Bearer <your token>"
      }
    }
  }
}

Vendor documentation: Cursor MCP.

Other tools

Any MCP client can connect. VS Code, Gemini CLI and your own scripts all work.

1. Look for MCP servers, connectors or integrations in the tool's settings.
2. Add a remote server of type Streamable HTTP with the server URL.
3. If the tool supports OAuth, it opens a NetFiscus sign-in page. Otherwise create a token and send it in a header.

Authorization: Bearer <your token>

Two technical notes. The server answers application/json only, so there is no SSE streaming. It supports the 2025-11-25 and 2026-07-28 protocol revisions.

File formats differ per tool. VS Code uses .vscode/mcp.json with "type": "http". Gemini CLI uses httpUrl.

Manage access

Open Settings, Connected apps in the app. You see two lists:

• Authorized apps. Every tool that signed in with your account.
• Personal access tokens. Every token you created, with its permissions and expiry.

Revoking either takes effect immediately. A password reset revokes everything at once.

Limits and safety

• Reading is free. Recording a balance, a deposit or a withdrawal costs credits, the same as in the app. Corrections are free, and a removal refunds credits.
• Before it changes or removes a record, the assistant shows it to you and waits for an explicit yes. Your tool asks for approval as well.
• Adding a balance always creates a new record. It never overwrites an older one. If the same date already has a value, you end up with two records, so ask your assistant to check first.
• An assistant cannot create, archive or delete an asset or a debt, and it cannot change your account settings. It cannot remove the last remaining balance of an asset or a debt either.
• Deposits and withdrawals belong to assets. A debt carries balances only.
• Access tokens are short lived and are stored only as a hash. We never store a token you can read back.
• The endpoint is rate limited, so a runaway assistant cannot hammer your account.
• A credential reaches one account only, yours. There is no admin access over MCP.

Troubleshooting

Authorization failed, or the tool cannot reach the server.
Check that the URL ends with /api/mcp. A URL without that path does not answer.

The tool reports 401 Unauthorized.
The token is revoked, expired, or the header is malformed. The header value must start with Bearer and a single space. Create a new token if you are unsure.

ChatGPT does not show the option to add a connector.
Developer mode is off, or your plan does not include it. See the OpenAI documentation linked above.

The assistant says a write failed for lack of credits.
Reading and correcting still work. Buy credits in the app to record new entries again.

The assistant refuses to remove a balance.
Every asset and debt keeps at least one balance. Correct the last one instead, or remove the asset itself in the app.

The tool expects a streaming connection.
Our server replies with plain JSON and no event stream. Configure the tool for Streamable HTTP with JSON responses.

See Also

• AI assistants overview
• Import and Export
• Security