# Expensify MCP connector

Connect Expensify to Elaichi and Claude, ChatGPT, Cursor, Microsoft Copilot or the Elaichi Agent can file expenses, build and export reports, mark them paid and update policies, each action under the signed-in person's own access and logged.

Source: https://elaichi.ai/connectors/expensify/

## Facts

| | |
| --- | --- |
| Application | Expensify |
| Category | Accounting |
| AI tools | 17 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Expensify is connected

- Mark the approved reports from last week as paid
- Export all reports for March for the auditors
- Create an expense for yesterday's client lunch on the Sales policy

## Connect Expensify in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Expensify.
2. Optionally set Share with, then press Connect.
3. Paste an Expensify API key. One person generates a token in Expensify and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Expensify tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Expensify MCP connector for Claude

Endpoint: https://api.elaichi.ai/mcp

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
4. Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

## Expensify MCP connector for Claude Code

Endpoint: https://api.elaichi.ai/mcp

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
```

Use `--scope project` instead to share it with the repository through `.mcp.json`.

## Expensify MCP connector for ChatGPT

Endpoint: https://api.elaichi.ai/mcp

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
3. Leave Authentication on OAuth, then tick the risk acknowledgement.
4. Press Create, then sign in and approve.

Works on the web. The plugin directory lives at chatgpt.com/plugins.

## Expensify MCP connector for Cursor

Endpoint: https://api.elaichi.ai/mcp

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

Set up per machine, so repeat it on each computer you work from.

## Expensify MCP connector for Microsoft Copilot

Endpoint: https://api.elaichi.ai/mcp

1. In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
2. Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
3. Create a new connection, sign in and approve, then press Add to agent.
4. Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.

Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.

## Connect Expensify to any MCP client

Endpoint: https://api.elaichi.ai/mcp

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

The Elaichi Agent already has these tools, with nothing to set up.

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Expensify tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Expensify through Elaichi

### Mark approved reports as paid after the run

Finance. Once the payment batch goes out, tell the agent which Expensify reports were covered and it marks them paid, so nobody is left chasing a reimbursement that already landed.

### Export reports and reconcile the card statement

Accounting. At month end, export the period's Expensify reports and build a reconciliation against the corporate card statement in one ask instead of a morning of clicking.

### Set up a policy for a new office

Operations. Create the Expensify policy, then adjust its categories, tags and report fields so the new team files expenses the same way everyone else does.

### Log the client dinner before you forget

Sales. Describe the dinner and the agent creates the expense in Expensify and drops it on a report, with the receipt file attached if you have it.

### Update employees in bulk after a reorg

People. When managers change or a department moves, update Expensify employee records in one pass rather than editing each person by hand.

### Put an expense rule in place

Finance. Tell the agent that rideshare charges always belong in Travel and it creates or updates the Expensify expense rule, so future submissions land in the right place.

## Elaichi vs Zapier MCP vs Composio for Expensify

All three can connect Expensify to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

| What to check | Elaichi | Zapier MCP | Composio |
| --- | --- | --- | --- |
| Where the AI connects | One address for the whole organization. Endpoint: https://api.elaichi.ai/mcp | A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Expensify tools | Allow or restrict single Expensify tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Expensify call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |

Sources: Zapier MCP [docs](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### How do I connect Expensify to Claude?

Two steps. In Elaichi, add the Expensify connector and paste in your Expensify API key, which is the only sign-in step and means there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you in to Elaichi and Expensify is available in the conversation.

### Does Expensify work with ChatGPT and Cursor as well as Claude?

Yes. The Expensify connector is exposed through one endpoint, https://api.elaichi.ai/mcp, and that same address works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect Expensify once in Elaichi and every client picks it up.

### What can an AI agent actually do with my Expensify data?

With Expensify connected, an agent can file an expense, create a report, export reports for a period, mark reports as paid and build a reconciliation. It can also list and create policies, update a policy's categories, tags, report fields and tag approvers, set expense rules, list domain cards, fetch a receipt file and update employees in bulk. Short, specific asks such as "mark report 4821 as paid" work better than long paragraphs.

### Does connecting Expensify give the AI access to every policy and report?

No. Every call to Expensify runs under the access of the person who signed in, so an agent sees the policies, reports and expenses that person could already see in Expensify. Elaichi can narrow that access further with roles and restrictions, and it can never widen it beyond what Expensify itself allows.

### Can my team share one Expensify connection?

Yes. One person connects Expensify with the API key, shares the connection with a team in Elaichi, and nobody else ever sees or handles that key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every Expensify action.

### Can I stop an agent from marking reports paid or changing policies in Expensify?

Yes. Restrictions in Elaichi work per action, so you can restrict marking Expensify reports as paid or editing policies for a role or for one person while leaving expense creation open. A restricted action still appears in Elaichi's tool search, flagged as restricted, but no client can run it, whatever the prompt says.

### What happens to an Expensify connection when someone leaves?

Offboarding a person in Elaichi ends their access to Expensify through every client at once. A shared Expensify connection keeps working for everyone else on the team. If you want the connection gone entirely, disconnecting Expensify once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client together.

### Does the Expensify MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Expensify is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

### Is Elaichi an alternative to Zapier MCP for Expensify?

Yes. Both let Claude, ChatGPT or Cursor use Expensify. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Expensify call.

### How is Elaichi different from Composio for Expensify?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Expensify: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 17 Expensify tools

Every tool below is callable through https://api.elaichi.ai/mcp once Expensify is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Expensify policies** (List). List the policies (workspaces) the authenticated user can access.
- **Get single Expensify policy by ID** (Get). Get one policy's categories, report fields, tags, tax rates and employees, keyed by policy ID.
- **Create a Expensify policy** (Create). Create a new policy (workspace).
- **Update a Expensify policy category by ID** (Update). Merge or replace a policy's categories.
- **Update a Expensify policy tag by ID** (Update). Replace a policy's tag levels and tags (inline JSON).
- **Update a Expensify policy report field by ID** (Update). Merge or replace a policy's report fields.
- **Update a Expensify tag approver by ID** (Update). Set or clear the approver for single-level tags on a policy.
- **Create a Expensify expense** (Create). Create one or more expenses in an employee's account.
- **Create a Expensify report** (Create). Create a report with expenses on a policy (must be enabled for the domain by Expensify).
- **Expensify reports export** (Export). Start a JSON export of reports and their expenses; returns the generated file name to pass to files.get.
- **Expensify reports mark as paid** (Action). Mark Approved reports as Reimbursed.
- **Get single Expensify file by ID** (Get). Download a file generated by reports.export or reconciliations.create.
- **Create a Expensify reconciliation** (Create). Generate a company-card reconciliation file for a domain (domain admins only) using your FreeMarker template; download it with files.get using file_system=reconciliation.
- **List all Expensify domain cards** (List). List the company cards assigned on a domain.
- **Expensify employees bulk update** (Update). Add, update or remove policy members in bulk (Advanced Employee Updater).
- **Create a Expensify expense rule** (Create). Create an expense rule for a policy member.
- **Update a Expensify expense rule by ID** (Update). Update an existing expense rule for a policy member.
