Satchel for AI assistants
Your business
account, now
inside your AI.
Connect your Satchel account to Claude, Cursor, or any assistant that speaks MCP. Ask about balances, review spending, trace a payment — in plain language, with no dashboard to open.
Works with the assistants you already use
Claude Code
Codex
Cursor
Manus
Gemini+ any MCP clientWho it's for
Built for complex, cross-border businesses.
- Dedicated IBANs.
- Physical & virtual cards.
- Multi-currency.
- Multi-account.
- Payment support.
What it does
Six hosted reads. One local write, disabled by default.
The sandbox uses the Satchel API contract with seeded, fictional data. Production use requires the applicable agreement, identification, verification and due diligence. Supporting documents may be requested. Authorised access is enabled only after those steps are completed and credentials are issued.
View account names, masked identifiers and balances through your assistant.
satchel_list_accounts: View account names, masked identifiers and balances through your assistant. Example — you: “What accounts do I have?” ai: Main EUR •••• 0001 €48,205.50 ★ master; Client funds •••• 0002 €212,500.00; USD Payouts •••• 0003 $131,020.00
satchel_get_balance: Total position, grouped by currency, computed on the fly. Example — you: “How much do we hold right now?” ai: EUR €260,705.50 (2 accounts); USD $131,020.00 (1 account); — total across 3 accounts
satchel_list_cards: Physical and virtual cards, masked and status-checked. Example — you: “Show our cards.” ai: Mastercard ••7781 EUR active; Visa ••4402 USD active
satchel_list_transactions: A human-readable ledger. Ask for the last N, any page. Example — you: “Show the last 5 transactions.” ai: -€18.40 [narrative withheld] Jul 15; -€4,200 [narrative withheld] Jul 14; -€63.18 [narrative withheld] Jul 14; +€12,900 [narrative withheld] Jul 13; +€48,000 [narrative withheld] Jul 01
satchel_get_transaction: Drill into a payment by id; narratives and counterparties need separate permission. Example — you: “Details on transaction 5015?” ai: #5015 +€48,000.00 EXECUTED; Narrative withheld by default; INCOMING · masked reference · Jul 01
satchel_financial_summary: Money in and out with unavoidable coverage limits; narrative heuristics are optional. Example — you: “Summarise last month's cash flow.” ai: In +€60,900 Out -€38,481 Net +€22,419; Merchant analysis withheld without narrative permission; Coverage: up to 200 recent transactions · verify source rows
satchel_move_money: Local stdio only; absent from hosted access and refused unless writes are explicitly enabled. Example — you: “Can this hosted connection move €5,000?” ai: Refused: the hosted server exposes read tools only; The local write tool is disabled by default; Payment capability requires a separate authorised configuration and decision
Automate the routine
Put the financial busywork on autopilot.
Your assistant can help with recurring, read-only tasks. Review each workflow and its outputs before relying on them for business decisions.
Scheduled workflows
Run it on a cadence — every Monday, at month-end, or when a threshold trips. Your assistant checks in so you don't have to.
you › Every Monday, summarise last week's cash flow and flag anything unusual.
Get the skillAutomate expense management
Categorise spend, match it to counterparties, and keep the ledger tidy — reviewed by you, not typed by you.
you › Categorise this month's card spend and list anything uncategorised.
Get the skillCreate reports with AI
Turn transaction data into a clear report on cash flow, counterparties and outgoings in plain language.
you › Build a Q3 cash-flow report and pull out the three biggest outflows.
Get the skillReports and reviews run read-only. Payment actions require authorised configuration and remain subject to applicable controls — see security.
Connect
One message. Then talk to your account.
No SDK, no JSON, no keys. Tell your agent to connect, approve with your email, ask.
- 01
Paste one message
Your agent connects itself.
- 02
Approve with your email
OAuth in the browser. Sandbox access follows successful authorization without manual review.
- 03
Ask about your money
Plain language, real API shapes.
- →The server every agent connects to
https://mcp.stchl.eu/mcp
Paste it. Approve in the browser. Done.
Security & compliance
The agent reads. You stay in control.
Hosted access is read-only and the sandbox uses fictional data. Payment capability is outside this hosted release and requires a separate decision.
Agent reads
It can analyse only the account data covered by the granted scopes. The hosted server exposes no payment tool.
You decide
You verify the source transactions and make any payment decision through an authoritative Satchel channel.
Access stays accountable
Successful live connections and allowed read-tool outcomes require persisted audit events, with connected-app revocation and an operator kill switch.
A live audit trail is a launch requirement, not a sandbox feature. Sandbox activity does not access real accounts or move real money.
Access controls
Real money. Locked down by default.
Giving an assistant reach into money is serious. Every capability is opt-in, every live account goes through proper onboarding, and the rails are EMI-licensed.
Verify decisions in Satchel
Hosted MCP output is informational. Verify source transactions and make payment decisions through an authoritative Satchel channel.
Read-only by default
The connector ships read-only. Payment actions require explicit authorised configuration and remain subject to the applicable service controls and permissions.
Short-lived sessions
The connector uses service session credentials and does not place a long-lived credential in chat history.
Onboarding and review
Live access requires the applicable agreement, identification, verification and due diligence. Supporting documents may be requested.
Sandbox-first
You start with seeded data that is fictional. Authorised live access is enabled through configuration only after the required agreement, identification, verification and due-diligence steps are completed and credentials are issued.
Get started
Try it with your agent. Go live with a person.
Connect your assistant
One click in the Connect section, your work email at the consent screen — and you're asking a live-shaped sandbox account about its money.
Talk to a personal manager
Request a conversation about the service and the information needed to assess your application.
Get onboarded and go live
Complete the required agreement, identification, verification and due-diligence steps. Supporting documents may be requested. Authorised live access is enabled through configuration only after those steps are completed and credentials are issued.