Full read-write Claude connector for Expensify
Have Claude build and code expense reports in Expensify
Stop assembling reports and keying in GL codes by hand. Claude pulls the matching expenses, drops them into a report, and tags them against the right policy, ready for you to submit in Expensify.
Expensify is an expense and spend management tool teams use to capture receipts, submit reports, and reimburse employees. People want Claude to do more than read expense data: to create reports, code expenses, and move reimbursements forward.
What is an Expensify MCP server?
A Expensify MCP server is a small hosted service that exposes Expensify's data and actions to Claude over the Model Context Protocol, so Claude can invoices, payments, and books inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Expensify's current connector do today?
Expensify ships an official Claude connector today, but it is read-only: it lets Claude search expenses and reports, summarize spending, and spot missing receipts, while it cannot create reports, code expenses, or move reimbursements. A custom Expensify connector adds the scoped write tools that fixed tool set leaves out, so Claude creates reports and codes expenses with human-in-the-loop approval instead of only reading exports.
What does full read-write Expensify access unlock?
Full read-write Expensify access lets Claude create expense reports, attach and categorize expenses, set the policy and tags, add comments, and hand back a finished report in Open status for you to submit. The report assembly and coding that used to mean manual data entry happen where the expenses already live.
- Create a new expense report and add matching expenses to it
- Categorize and tag expenses against the correct policy and GL codes
- Add a comment or note to flag an expense for review
- Mark an already-approved report as reimbursed after you confirm
- Pull expenses matching a query and draft a report grouped by project
Can Claude create an expense report in Expensify?
Yes. With a full read-write Expensify connector, Claude can create a new expense report, pull the matching expenses, and add them to it. It groups and assembles the report where the expenses already live, so the data entry that used to be manual happens for you, ready for review.
Can Claude categorize and code expenses in Expensify?
Claude can categorize and tag expenses against the correct policy and GL codes, and add a comment or note to flag anything for review. The coding runs as a scoped write tool against your own account, so it never reaches policies or data your Expensify login cannot already touch.
Will Claude submit a report for approval in Expensify?
No. The Expensify API has no submit-for-approval step, so Claude assembles and codes the report and hands it back in Open status. You do the final submit yourself in Expensify. Claude can also mark already-approved reports as reimbursed when you confirm, so nothing moves money by surprise.
How an Expensify connector works
We build a small MCP server that authenticates to Expensify through its Integration Server credentials or scoped API access, using the narrowest permissions the work needs. Read tools (list expenses, fetch reports) and write tools (create report, code expense, mark approved as reimbursed) are separated, and reimbursement-moving actions require your confirmation. Claude only ever has the access your own Expensify account already has, and the server can run behind IP allowlisting where your policy requires it.
Frequently asked questions
Can Claude create and code expense reports in Expensify, not just read them?
Will Claude move a reimbursement in Expensify without my approval?
Does the Expensify connector get more access than my own account?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.