Connect an AI assistant to Memo Bank with the MCP server

The Memo Bank MCP server lets AI assistants (such as Claude, Gemini, ChatGPT and others) securely query, analyze, and enrich your banking data. This guide explains how to activate the connector, what it can and cannot do, and how your data is protected.

MCP in a nutshell

The Model Context Protocol (MCP) is an open standard that lets AI assistants connect to external services. An MCP server exposes a set of tools the assistant can call on your behalf.

The Memo Bank MCP server is Memo Bank’s official remote MCP server. Once activated, your AI assistant can:

  • list your workspaces, accounts, IBANs, and transactions;
  • search and filter transactions by date, counterparty, IBAN, batch, or custom ID;
  • download and upload supporting documents attached to transactions.

Write access is limited to documents: the assistant can read your banking data and attach supporting documents to transactions, but it cannot initiate payments, move money, or modify existing transactions.

The Memo Bank MCP is designed for any MCP-compatible client can connect to it using the same OAuth flow.

Prerequisites

Before you activate the connector, make sure you have:

  • an active Memo Bank business account;
  • access to the Memo Bank workspace(s) you want the assistant to work with;
  • an MCP-compatible AI assistant, or any client that supports remote MCP servers.

Configure and activate the Memo Bank MCP

MCP URL: https://api.memo.bank/api/apps/mcp/server    

In a desktop or web application

  1. Open Settings     → Connectors     in your AI tool (the exact location may vary). You may need an admin role to add connectors.
  2. Click Add connector     and select Memo Bank     from the directory, or add it manually with the server URL above.
  3. Your AI tool opens the Memo Bank authorization page in a new tab.
  4. Sign in with your Memo Bank credentials and complete two-factor authentication.
  5. Select the workspace(s) you want to authorize, then click Authorize  .
  6. You are redirected back to your AI tool, which confirms the connector is active.

In a command-line tool

  1. ↓
claude mcp add --transport http --scope user memobank https://api.memo.bank/api/apps/mcp/server
  1. Restart your session and run /mcp  to authentify.

OAuth 2.0 flow

The Memo Bank MCP uses the OAuth 2.0 authorisation code flow to let you grant access to your banking data without ever sharing your Memo Bank password with the AI.

The flow in four steps:

  1. Redirect to Memo Bank. Your AI tool redirects your browser to Memo Bank's authorisation endpoint.
  2. Authentication. You sign in with your Memo Bank credentials and complete second-factor authentication.
  3. Consent. Memo Bank displays the list of workspaces you have access to. You pick which workspace(s) the Claude connector is allowed to act on.
  4. Callback. Memo Bank redirects you back to the AI tool with a short-lived authorisation code, which is then exchanged for a refresh token and an access token . These tokens are stored securely and used to authenticate every subsequent tool call.

Only the workspaces you explicitly selected during step 3 will be reachable through the AI — every other workspace on your Memo Bank account stays invisible to the model.

The Memo Bank consent screen listing the workspaces the user is authorising
The Memo Bank consent screen listing the workspaces the user is authorising

Permissions and accountability

All requests made through the Memo Bank MCP are executed on behalf of the user who activated the connector via the OAuth 2.0 flow.

That means:

  • The AI acts with your exact permissions on the authorised workspaces. No more, no less.
  • Any tool call (reading transactions, uploading a document) is attributed to your user in Memo Bank's audit log, exactly as if you had performed the action yourself from the web app.
  • You remain fully responsible for the actions the AI takes on your behalf. Always review what the AI intends to do before confirming a write operation (for example, attaching a document to a transaction).
  • You can revoke the connector at any time from your Memo Bank workspace settings (see "Deactivate" below), which immediately cuts the AI access.

We recommend treating the Memo Bank MCP like any other automation running with your credentials: only authorise it on workspaces you own, and keep an eye on the audit trail.

Deactivate the connector

You can disconnect the Memo Bank MCP from either side.

  • From your AI tool (removes the connector and its tokens):
  1. Open Settings   → Connectors .
  2. Find the Memo Bank connector in the list.
  3. Click Disconnect   (orRemove ).
  • From Memo Bank (revokes access for all clients using this connection):
  1. Log in to your Memo Bank workspace.
  2. Go to Applications .
  3. Find the MCP in the list and click deactivate.

MCP Authorization list

On the next tool call, your AI tool will report that access was revoked and prompt you to authorize again.

Available tools

Tool What it does Type
list_workspaces     Lists the Memo Bank workspaces you have authorised this Claude connector to act on. Read
list_accounts     Lists all bank accounts in a workspace (current accounts, dedicated accounts, etc.) with balance, IBAN, and status. Read
list_ibans     Lists all IBANs associated with a workspace's accounts, including virtual IBANs. Optionally filtered by account. Read
list_transactions     Lists transactions with rich filters: account, date range, reference, local IBAN (useful for virtual IBAN tracking), batch, custom ID, and sort order. Read
list_attachments     Lists supporting documents attached to transactions. Can be filtered by transaction. Read
get_attachment     Returns metadata and a pre-signed download URL for a specific attachment. Read
create_attachment     Returns a pre-signed upload URL to attach a new supporting document (invoice, receipt…) to an existing transaction. Write

All read tools are annotated with readOnlyHint: true , so the assistant knows they are safe to call without explicit confirmation. create_attachment  is annotated as a non-destructive write, so the assistant will typically ask for confirmation before calling it.

Hands-on examples

Below are three prompts you can try once the connector is active. Each one showcases a different capability. Screenshots below are taken using Claude Code as CLI, but the same use cases apply to any MCP client.

Example 1: Monthly summary

A quick, read-only way to get a pulse check on your accounts.

Prompt:

Using Memo Bank, give me a summary of last month’s activity on the Compte principal: total money in, total money out, net change, and the top 5 outgoing counterparties as a markdown table.

What the AI does:

  • Calls list_workspaces  then list_accounts  to locate Compte principal.
  • Calls list_transactions  with the account and date range.
  • Aggregates credits, debits, and the top outgoing counterparties into a clean summary.

Example 2: Transactions missing a supporting document

Useful for month-end close: find every outgoing transaction over a given amount that has no invoice attached yet.

Prompt:

Using Memo Bank, list every outgoing transaction on the Compte principal executed in March 2026 above €500 that has zero attached documents. Return a markdown table with execution date, counterparty, amount, and the transaction reference.

What the AI does:

  • Calls list_transactions    filtered by account, date range, and direction.
  • Filters client-side on attachment_count == 0  for debits ≥ €500.
  • Returns an actionable table your accounting team can work from.

Example 3: Auto-attach supporting documents to the matching transactions

Drop a folder of PDF invoices into the chat, or retrieve it directly from your invoicing tool and let the AI match each one to the correct transaction and attach it automatically.

Prompt:

Using Memo Bank, for each PDF invoice I just shared: 1. Read the invoice to extract the supplier name, amount, and invoice date. 2. Find the matching outgoing transaction on the Compte principal (within ±5 days of the invoice date, same amount, matching counterparty). 3. Attach the PDF to that transaction using create_attachment. 4. Return a markdown table summarising: invoice file, matched transaction reference, status (attached / not matched / ambiguous). Ask me to confirm before uploading anything if there is any ambiguity.

What the AI does:

  • Reads each invoice PDF shared in the conversation.
  • Calls list_transactions  for each invoice to find the matching operation.
  • For each confident match, calls create_attachment  to get a pre-signed upload URL, then PUTs the PDF to it.
  • Surfaces anything ambiguous for your review instead of auto-uploading.

For safety, the create_attachment  tool is annotated as a write, so Claude will typically ask for confirmation by default, but an explicit instruction in the prompt guarantees it.

Security and data handling

  • Transport. All communication between AI and Memo Bank uses HTTPS/TLS.
  • Authentication. OAuth 2.0. Memo Bank credentials never leave Memo Bank; the AI only ever holds short-lived access tokens and refresh tokens.
  • Scope. The AI can only see the workspaces you explicitly authorised. Other workspaces on your Memo Bank account are invisible.
  • No write access to banking operations. The AI cannot initiate a transfer, modify a transaction, or change any account setting. The only write capability is attaching supporting documents.
  • Audit trail. Every tool call is logged in Memo Bank's audit log under your user, just like an action performed from the web app.
  • GDPR. Memo Bank is a French licensed bank, supervised by the ACPR. All personal data is processed in compliance with the GDPR — see our Privacy Policy for details.

What the MCP cannot do for now

  • No payment initiation. It cannot transfer money, create SEPA credit transfers, or trigger any cash movement.
  • No transaction modification. It cannot edit, cancel, or delete existing transactions.
  • No account or user management. It cannot create accounts, IBANs, or users, nor change permissions.
  • No access outside the authorized workspaces, even if you belong to other workspaces.