Skip to main content

Finaloop MCP: common issues and fixes

Find your symptom and the fix, from sign-in failures to numbers that don't match your reports.

Written by Emily Burrows

About

Most Finaloop MCP problems come down to one of four things: your role doesn't have access, your AI tool needs to sign in again, the figure you're comparing came from your sales data rather than your books, or your result hit a row limit. Find your symptom below and follow the matching fix.

This article covers connecting and signing in, getting answers, working with results too large for one response, and changes that get refused.

Who is this for? The Finaloop MCP is in beta. You can connect it if your Finaloop role is Admin, CFO, Tax CPA/Accountant, or Operator/VA – Full access. If you haven't connected yet, start with Connect Finaloop to Your AI Stack.

Symptoms

Connecting and signing in

  • I get a message saying my role doesn't have access

  • I don't see an option to add a custom connector

  • I have more than one company connected and it's showing me the wrong one

  • It worked yesterday and stopped today

Getting answers

  • I've connected, but I don't know what to ask

  • It says it can't find my data, or comes back empty

  • The numbers don't match what I see in Finaloop

Large results and exports

  • My results stopped at 1,000 rows

  • My ledger pull came back in pieces

  • My export isn't ready, or won't start

  • My download link stopped working

Making changes

  • It asks my permission for every single question

  • It won't make a change I asked for

  • It won't touch my loans

  • I get an error message when creating a Purchase Order


1. Connecting and signing in

"I get a message saying my role doesn't have access"

What you're seeing: You add the connector, start to sign in, and Finaloop shows a message that your role can't use the MCP.

Why it happens: In Finaloop the MCP is limited to four roles: Admin, CFO, Tax CPA/Accountant, and Operator/VA – Full access.

How to fix it:

  1. Check your role with the Admin on your Finaloop account.

  2. If your role isn't on the list, ask your Admin to change it, or to run the request for you.

  3. Add the connector again once your role is updated.

You'll know it worked when the sign-in window closes on its own and the connector shows as connected.

"I don't see an option to add a custom connector"

What you're seeing: No Add custom connector option in Claude, or no Create option in ChatGPT.

Why it happens: Both tools gate custom connectors behind their own plans and settings, not Finaloop's.

How to fix it:

  • In ChatGPT: custom connectors need a paid plan, and Developer mode has to be turned on in Settings → Apps → Advanced settings before Create appears.

  • In Claude: custom connectors are added under Customize → Connectors. [VERIFY: which Claude plans expose custom connectors — this changes and shouldn't be stated from memory.]

Claude, ChatGPT and Cursor all support custom connectors, as do command-line tools like Claude Code and Codex. If the option is still missing in yours, that's a question for their support rather than ours.

You'll know you're past this step when the connector appears in your AI tool's list and asks you to sign in.

"I have more than one company connected and it's showing me the wrong one"

What you're seeing: You have access to more than one company in Finaloop, and the answers are about the wrong one.

Why it happens: Your sign-in sets one active company for that connection, and it doesn't follow the company you're looking at in the Finaloop app.

How to fix it:

  1. Ask the AI tool to list the companies you have access to.

  2. Name the company you want in your question, and ask it to use that company's ID.

  3. If it still answers about the wrong one, remove the connector and sign in again — the company you're signed into becomes the active one.

You'll know it worked when a question you can check, like what's my revenue year to date?, returns the right company's numbers.

Tip: If you work across several companies daily, say the company name in the first message of each conversation. It costs you a sentence and saves you a wrong answer.

"It worked yesterday and stopped today"

What you're seeing: Answers that used to come from your books now don't, with or without an error.

Why it happens: The sign-in behind the connector has expired or been revoked.

How to fix it:

  1. Remove the Finaloop connector in your AI tool.

  2. Add it again with https://mcp-api.finaloop.com.

  3. Sign in with your Finaloop credentials.

  4. Check your Tool permissions, and if your read tools have reverted to asking every time, set them back.

You'll know it worked when Fetch my P&L year-to-date returns your numbers again.


2. Getting answers

"I've connected, but I don't know what to ask"

What you're seeing: The connector is live and you haven't used it.

Why it happens: Nothing's wrong. This is the most common state after setup, and a blank prompt box is a hard place to start from.

How to fix it: Start with Fetch my P&L year-to-date to confirm it's working, then pick a question from What you can ask the Finaloop MCP, it's organized by job, so you can jump to sales, margin, spend, or ads and paste a prompt straight in.

"It says it can't find my data, or comes back empty"

What you're seeing: The tool responds that it has no data, or returns an empty report.

Why it happens: Usually the connector is added but not authorized, or the period you asked about genuinely has nothing in it.

How to fix it:

  1. Ask a question you know has an answer: Fetch my P&L year-to-date.

  2. If that returns nothing, remove the connector and add it again, signing in when prompted.

  3. If it returns a P&L but your original question didn't, narrow the question — name the period and the breakdown explicitly.

You'll know the connection itself is fine as soon as the P&L comes back with numbers in it. Anything still missing after that is a question of period or phrasing, not of the connection.

Tip: An empty answer for a recent period often means a sales channel or bank connection hasn't synced. Check the same period in Finaloop first; if it's empty there too, the MCP is reporting your books correctly and nothing is broken on the AI side.


"The numbers don't match what I see in Finaloop"

What you're seeing: A figure from the AI tool differs from the same figure in your reports.

Why it happens:

  • You got your sales data instead of your books, or the other way around. Revenue lands in your books when an order is fulfilled, so a day with unfulfilled orders shows sales in one and nothing in the other. See What the Finaloop MCP can see and change.

  • A different date range than the report you're comparing against.

  • A different timezone, or the accounting method.

How to fix it:

  1. Ask which numbers it used: Was that from my books or my sales data, and what date range?

  2. Re-ask with both stated: From my books, on an accrual basis, revenue for August 1 to 31, 2026.

  3. If it still differs, ask which transactions make up that number? and compare that list against the same period in Finaloop.

Nine times out of ten the source or the period turns out to be different, and re-asking with both stated gives you a figure that matches your report exactly. If the transaction lists match but the totals still don't, send it to us — see Still stuck? below.

Important: Before you trust a total, check it wasn't built on a truncated list. See section 3.


3. Large results and exports

"My results stopped at 1,000 rows"

What you're seeing: An analytics answer covering fewer rows than you expected.

Why it happens: Analytics queries return at most 1,000 rows. The response says so — it comes back marked as truncated, with a hint about narrowing the query — so your AI tool can tell you rather than quietly cutting the list short.

How to fix it, in the order worth trying:

  1. Aggregate instead of listing. Total sales by month is 12 rows where every order is thousands. Most questions don't need the rows at all.

  2. Filter harder. One channel, one product, one month at a time.

  3. Ask for an export. For anything that genuinely needs every row, ask for it as a file rather than in the chat. See below.

You'll know you're clear of the limit when the answer comes back without the truncation flag, or when you have the export file in hand.

Important: Rephrasing doesn't help. The limit is a row count, not a matter of wording, and a total your AI tool adds up from a truncated list is wrong in a way that's hard to spot. If completeness matters, like a tax total, a filing, a reconciliation, export it.

"My ledger pull came back in pieces"

What you're seeing: Ledger transactions arriving 100 at a time, with the AI tool fetching more.

Why it happens: Ledger detail is paged at 100 rows per page. This is normal and your AI tool will keep asking for the next page on its own.

How to fix it: Nothing, if you're willing to wait. It's working as intended. For a long period, narrowing the date range or exporting is faster than paging through thousands of rows.

"My export isn't ready, or won't start"

What you're seeing: You asked for a ledger or report export and it isn't there, or the request is refused.

Why it happens: Exports run in the background, so they aren't instant. A company can run 2 exports at a time; a third has to wait for one to finish.

How to fix it:

  1. Ask for the status of your exports.

  2. If two are already running, wait for one to finish before starting another.

  3. If you only need a summary, ask for the aggregated numbers instead — those come back in the chat straight away.

You'll know it worked when the export is listed as ready and you're given a download link.


"My download link stopped working"

What you're seeing: An export download link that returns an error.

Why it happens: Download links expire 10 minutes after they're issued.

How to fix it: Ask for the link again. The file itself is still there; only the link expired, and the new one downloads the same export.

Tip: Ask for the export first and download it when it's ready, rather than coming back to an old chat later. The link in a conversation from yesterday won't work.


4. Making changes

"It asks my permission for every single question"

What you're seeing: An approval prompt before every answer, including simple report pulls.

Why it happens: This is the default, and it's a setting rather than a fault.

How to fix it: Set your read tools to run without asking, and leave everything that creates, updates, categorizes, deletes, disconnects or sends on Ask every time. See What the Finaloop MCP can see and change.

"It won't make a change I asked for"

What you're seeing: The tool declines, or says it doesn't have permission.

Why it happens: Usually the change tools are switched off in your connector settings, or the approval prompt appeared and went unanswered.

How to fix it:

  1. Check the connector's Tool permissions and confirm the tool you need is enabled.

  2. Ask again, and approve the prompt when it appears.

  3. Open the record in Finaloop to confirm the change saved.

You'll know it worked when the change is there in Finaloop.

"It won't touch my loans"

What you're seeing: Any request to create, change or delete a loan is refused.

Why it happens: Loans are deliberately out of the MCP's reach. This isn't a permissions setting and there's nothing to turn on.

How to fix it: Manage loans in the Finaloop app. The refusal message points you to the loans page.

"I get an error message when creating a Purchase Order"

What you're seeing: This error, verbatim, when you ask the AI tool to create a Purchase Order (PO).

Why it happens: Purchase Orders need unit-level inventory tracking, which comes with InventoryIQ. Without it there's nothing for the PO to track units against.

How to fix it: Set up InventoryIQ in the app. Once it's on, ask again and the PO will be created. Nothing is wrong with your connection or your prompt.


Still stuck?

If you've re-added the connector and it still won't sign in, or a figure is wrong even though the transactions behind it match, reach out to our Support team through chat or at [email protected]. Include these five things so the first reply is an answer rather than a question:

  • Which AI tool and surface you're using (Claude web, Claude desktop, Claude mobile, Claude Code, or ChatGPT)

  • The exact prompt you sent

  • The exact error text, copied rather than described

  • The email address on your Finaloop account and your role

  • Roughly when it happened, with the date


Related articles

Did this answer your question?