Expensify MCP server for Claude, ChatGPT and Cursor: what it reads, access, how to connect
Expensify hosts one read-only MCP server, also listed as a Claude connector and a ChatGPT plugin, that searches the expense data you can already see. Verified 21 Oct 2026.
- Official remote MCP · read-only
- Claude connector · read-only
- ChatGPT plugin · read-only
- Hosting
- Remote, hosted by Expensify at https://www.expensify.com/mcp (Expensify's Claude and Cursor guides add a trailing slash). No local or open-source server.
- Auth
- OAuth 2.1 with PKCE; you sign in to Expensify and approve a consent screen. Expensify says the AI client gets neither your password nor a long-lived API key.
- Read / write
- Read-only. Expensify says the assistant cannot create, edit or delete anything in Expensify.
- Works with
- Expensify publishes guides for Claude, ChatGPT and Cursor; its blog also names OpenClaw, and its help centre says other MCP clients may work.
- Plan requirement
- Any member with an Expensify account; Expensify says no admin seat or contract is needed. Pricing for MCP access is not stated.
- Last changed
- July 2026 (Claude directory listing added)
- Verification
- Verified 21 Oct 2026 by theFinanceStack · confidence: high
What can an agent do with Expensify through MCP?
It can search and summarise the Expensify data your own login can already see. Expensify documents 1 tool for this, Search. It can't approve, edit, reimburse or change settings.
Expensify's guides describe a single Search tool that retrieves and filters data so the assistant can analyse it.
What it can search
Expensify lists these as searchable:
- Expenses, reports and reimbursements
- Invoices, merchants, categories and receipts
- Approvals and Workspace data
- Trips, chats and tasks
- Spend trends
Good to know
- The Claude directory listing names 3 tools:
GetCurrentUser,GetWorkspaceListandSearch, without descriptions. - What the server returns is limited by your existing account and Workspace permissions, per Expensify.
- Expensify's blog calls access read-only "at launch" and publishes no plan for write actions.
Can
- Search expenses and expense reports in plain language
- Summarise spending by merchant, category or period, and analyse spend trends
- Find expenses with missing receipts
- List reports waiting for your approval (it finds them; you can't approve them through MCP)
- Look up invoices, reimbursements, trips, tasks and Workspace details you have access to
- Identify the signed-in user and list their Workspaces (per the Claude directory tool names)
Cannot
- Create, edit or delete anything in Expensify, per Expensify
- Approve reports, reimburse payments or manage Workspace settings, per Expensify
- Lock cards or move money, per Expensify's launch blog
- See data beyond what the signed-in member can already see in Expensify, per Expensify
What access does it get?
Read access to whatever the signed-in member can already see, granted through one OAuth scope, mcp:tools.
| Where | Scopes and permissions (as documented) | Admin requirement |
|---|---|---|
| Expensify MCP server (remote) | mcp:tools, granted on OAuth 2.1 approval (with PKCE). Expensify says it gives read access to data the user can already see under their account and Workspace permissions. | None documented by Expensify: any member with an Expensify account can connect. The AI client's own rules apply (see the Claude and ChatGPT rows). |
| Claude connector (Claude directory) | Same server and mcp:tools scope; the listing shows sign-in as required. Per-tool permissions are not documented by the vendor. The listing is marked Anthropic verified. Anthropic says it doesn't control which tools developers provide or check that they won't change. The listing's 3-tool list already differs from Expensify's 1-tool description, so check the live tool list after connecting. | Expensify says Claude Owners can make the connector available to an organisation. Claude Team/Enterprise: an Owner adds connectors and may restrict Claude Code MCP servers. Expensify notes Claude Free plans support one custom connector. |
| ChatGPT plugin | Same server; you click Allow and finish the OAuth approval in your browser. Scope names are not shown in the ChatGPT guide. | Expensify doesn't document ChatGPT plan or admin rules. ChatGPT Business/Enterprise: an admin must allow the app. |
How do I connect it?
Add the Expensify connector or plugin in your AI client, or point any MCP client at https://www.expensify.com/mcp, then sign in to Expensify and approve the consent screen. In Cursor 0.46 or newer, Expensify's guide adds it under Cursor Settings › Tools & MCPs › New MCP server with the URL https://www.expensify.com/mcp/, then you sign in on first use.
- Open the Expensify listing at https://claude.com/connectors/expensify and click Add to Claude.
- Or add a custom connector (in Claude: Customize › Connectors) with the server URL Expensify's guide gives, https://www.expensify.com/mcp/.
- Sign in to Expensify in the browser window, review the permissions and click Approve.
- Ask a question that needs Expensify data to test it. On Claude Team/Enterprise, an Owner adds the connector for the organisation.
If Claude can't reach your data, Expensify suggests checking the URL, restarting the connector and reauthorising.
What should a finance team watch for?
The server can't change your books. The risks are in what the assistant reads and passes on, and in whether its summaries are accurate.
- Expensify says the server is read-only by design. Approvals, reimbursements and expense edits still happen in Expensify itself.
- Each person sees only what their own login can see, so an employee and a Workspace admin will get different answers to the same question.
- Expensify doesn't publish rate limits, result caps or tool descriptions, so you can't tell whether a large search returned everything; tie any totals to Expensify's own reports.
- Expense comments, chats, merchant names and task text are untrusted input. An instruction hidden in one could steer the agent, for example toward a write-capable tool connected in the same chat, so keep human approval on for those tools. An injected instruction could also ask the agent to paste Expensify data into another connected tool that sends messages or fetches URLs, so keep approval on for outbound tools as well.
- Expensify's MCP pages make no statement on data retention or model training; read Expensify's privacy policy and your AI vendor's terms before connecting.
- To revoke access, remove the connector in your AI client; Expensify also mentions its own OAuth revocation where your client supports it.
How could finance teams and accounting firms use it?
The server is read-only, so it suits questions, reviews and reporting on spend. Any action still happens in Expensify.
Inside a company
- Ask which expenses this month are missing receipts before the close cut-off.
- Summarise spend by category or merchant for a department budget review.
- List reports waiting for your approval, then approve them in Expensify.
- Draft the expenses section of the monthly management pack, then tie the figures to Expensify reports.
At an accounting firm
- Prepare for a client review by summarising that client's spend trends and top merchants.
- Run month-end questions on unreimbursed reports and missing receipts for a client Workspace your login can see.
- Pull a client's travel and trip spend for an expense-policy review.
- List a client's open invoices and reimbursements before a month-end call.
Keep a person approving anything that changes the ledger or Expensify, and treat AI-drafted figures as drafts until they tie to Expensify's reports.
Want Expensify connected to Claude for your team?
We configure scoped connections and a review step before anything changes your books. Fixed fee.
Book a 30-minute setup callChange log
| Date | Change | Source |
|---|---|---|
| 2026-07 | Expensify connector added to the Claude directory, listing GetCurrentUser, GetWorkspaceList and Search | claude.com/connectors/expensify |
| 2026-06-24 | Expensify blog post details OAuth 2.1 with PKCE, the single Search tool and read-only access at launch | use.expensify.com/blog/expensify-mcp |
| 2026-06-08 | Expensify announces its MCP server for ChatGPT, Claude, Cursor and other MCP clients | www.cpapracticeadvisor.com/2026/06/08/expensify-launches-mcp |
FAQ
Is this official?
Yes. Expensify built and hosts the MCP server, announced it on 8 June 2026, and is the listed developer of the Claude connector.
Is it free?
Expensify says no admin seat or contract is needed; any member with an Expensify account can connect. It doesn't state MCP pricing. You also need an AI client plan that allows connectors.
Does it change data in Expensify?
No. Expensify says the assistant cannot create, edit or delete anything, and cannot approve reports or reimburse payments.
Is my data used to train models?
Expensify's MCP pages don't address training or retention. Check Expensify's privacy policy and your AI provider's terms before connecting.
Can my accountant use it on my behalf?
Expensify doesn't document this. It says access follows the signed-in member's own permissions, so an accountant would connect with their own Expensify login and see only what that login can see.
Sources
- Expensify Help: Use the Expensify MCP server with AI assistants
- Expensify Help: Connect Claude to Expensify using MCP
- Expensify Help: Connect ChatGPT to Expensify using MCP
- Expensify Help: Connect Cursor to Expensify using MCP
- Claude directory: Expensify connector
- Expensify blog: Expensify MCP (24 June 2026)
- CPA Practice Advisor: launch coverage (8 June 2026)
- Expensify privacy policy
Verified by theFinanceStack, 21 Oct 2026. Vendor list on the CFO Software Market Map courtesy of Jason Staats; AI connectivity data by theFinanceStack. Not tax, compliance or financial advice.