Talk to your expenses: connect Mylo to your AI assistant

Your expense data has always lived behind an app UI. Want the receipts from a trip? Open the app, tap Filters, set a date range, scroll. Want to know what you spent at one vendor this quarter? More taps. The data is yours, but the interface decides how you get to it.

Now there's a second door. Mylo ships a connector for AI assistants: connect it to Claude (or another MCP-compatible assistant, including ChatGPT where custom connectors are available) and your expenses become something you talk to.

Ask like you'd ask a person

Once connected, your assistant can search your Mylo data the way you actually think about it:

> "Find my receipts from the New York trip, June 2–5."

> "How much have we spent at Starbucks this quarter?"

> "Which vendors did I spend the most with this year?"

> "Any card transactions over $200 last month that I haven't expensed yet?"

No filters to build, no export-to-spreadsheet detour. The assistant searches your receipts by text, date, merchant, amount, sender, or currency; digs into line items on any single receipt; aggregates spend by vendor; and searches your linked bank and card transactions, including which ones already became expenses and which didn't.

Not just answers: actions

Here's the part that changes the workflow: the assistant doesn't just read. Give it permission and it can act:

> "Great, create an expense report called 'New York trip' and add expenses > for all of those receipts."

One sentence, and Mylo creates the report and turns every receipt into an expense attached to it. The assistant can also:

• Create individual expenses: "add a $40 expense for yesterday's client lunch at Balthazar, category Meals."
• Create mileage expenses: give it a distance or odometer readings, and Mylo computes the amount from your organisation's mileage rate.
• Create and edit spending policies: the documents Mylo automatically checks new expenses against.

Everything the assistant creates lands as a draft. Nothing gets submitted to an approver behind your back: you review and submit in the app, exactly like a draft you created yourself. Your assistant does the assembly; you keep the sign-off.

The month-end scenario

You're back from three days in Boston. Instead of the filter-select-create dance, you type one message:

> "Find my receipts from June 10–13, create a 'Boston client visit' report, > and add expenses for all of them."

The assistant searches the date range, creates the report, drafts an expense from each receipt, and shows you the report total. You open Mylo, glance over the drafts, and submit. A trip's worth of paperwork, done in a chat message.

Your data stays yours

The connector is built so this stays safe and boring:

• You sign in with your own Mylo account. The connection is authorized through a standard OAuth sign-in and a consent screen that tells you exactly what the assistant will be able to do, before you allow it.
• The assistant sees only your data. Every request runs scoped to your account. There's no path to anyone else's receipts or transactions.
• Read and write are separate permissions. A read-only connection can search and answer, but every create/edit tool refuses to run.
• Writes create drafts, and assistants ask first. Claude asks you before running an action that changes data, and even then, the result is a draft you review in Mylo.
• Revoke anytime. One tap in Settings → AI assistants disconnects an assistant, and access ends immediately.

Works where your assistant works

Mylo's connector is a remote MCP server, the open standard for connecting AI assistants to tools. It works with Claude on web, desktop, and the mobile apps via custom connectors, and with other MCP-compatible assistants, including ChatGPT where custom connectors are available on your plan.

Ready to try it? The step-by-step setup (including exactly what tools the assistant gets and how permissions work) is in Connect Claude (or ChatGPT) to Mylo.