Skip to main content

My connection to the Finary MCP fails

Written by Raji

Common problems

  • The URL is missing the https:// prefix. The URL must start with https://: without it, your client falls back to http:// and the connection is refused.

  • You're using a VPN. Some VPNs trigger a security check that makes the connection fail. Turn it off while you connect Finary, then turn it back on.

  • "Authorization with Finary failed": first check that Allow AI assistants (MCP) is turned on under Security in your Finary account menu. If it is, the connector's access has probably been removed: authorise again (see below). If the message shows a reference starting with ofid_, send it to us: it helps us track down the attempt.

  • The connector shows as connected but no tools appear: close and reopen your assistant. If the problem persists, contact us.

  • Your assistant keeps asking you to authorise again, or the authorisation goes through and then fails straight away: contact us, telling us which assistant you're using and the exact time of your last attempt. With those two details, we can find your attempt in our logs.

  • Your assistant says it can't access your transactions: either you didn't allow this access (authorise again), or your plan doesn't include Budget (Giving my AI assistant access to my transactions).

  • Your assistant says it can't create or change your data: you may not have granted this access (authorise again). If it refuses to do something on one particular account, that account may be an older manual account or a synced account (Allowing my AI assistant to change my Finary data).

Authorise again

If you want to add access (to transactions or changes), or if you've cut off access, simply reconnecting isn't enough: you need to authorise again.

  1. Remove the Finary connector from your assistant (How do you cut off access?).

  2. On the Finary authorisation screen, tick what you want to allow, then click Authorize read-only access (or Authorize access if you allowed changes).

Still stuck?

Contact us, telling us which assistant you used and the message you saw: that's what we need to get you up and running.

Did this answer your question?