Connect your AI Agents to Expensify in minutes

What is an Expensify MCP?

It's an MCP server that lets your agents access data and functionality from Expensify via tools. Your agents can invoke these tools to pull expense reports, submit expenses, reconcile corporate card transactions, manage spend policies, and more.

Expensify doesn't offer an official MCP server, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the Expensify MCP server?

The use cases naturally depend on the agent you've built, but here are a few common ones:

• Automated expense submission. When a sales rep logs a client dinner in your CRM or books travel through a third-party tool, your agent can automatically create the corresponding expense in Expensify, categorize it against the right policy, and attach it to the relevant report

• Corporate card reconciliation. On a nightly or weekly schedule, your agent can export card transactions, cross-reference them against submitted reports, and flag any unmatched charges for finance team review before month-end close

• Policy compliance checks. When a new report is created, your agent can retrieve the applicable spend policy, validate each line item against category limits and approval thresholds, and surface violations before the report reaches an approver

• Finance reporting to stakeholders. Your agent can pull expense reports across teams or cost centers on a recurring cadence, aggregate spend by category, and post a formatted summary to a Slack channel or Google Sheet for leadership review

What are popular tools for Expensify's MCP server?

Here are some of the most commonly used tools:

• <code class="blog_inline-code">export_reports</code>: retrieves expense reports from Expensify filtered by date range, employee, or policy — the primary tool for reconciliation agents and finance summary workflows

• <code class="blog_inline-code">create_expenses</code>: submits one or more expense line items to an existing report, used when agents need to log expenses automatically based on an external trigger

• <code class="blog_inline-code">export_card_transactions</code>: pulls corporate card transaction data for a given domain and date range, enabling agents to identify unreconciled charges or flag out-of-policy spend

• <code class="blog_inline-code">create_report</code>: opens a new expense report under a specified policy, useful when agents need to group expenses into a fresh report before submitting for approval

• <code class="blog_inline-code">update_report_status</code>: advances or reverts a report's status in the approval workflow, allowing agents to programmatically submit, approve, or reopen reports based on business logic

• <code class="blog_inline-code">list_policies</code>: returns all spend policies available in the account, giving agents the context they need to validate expenses or assign new reports to the correct policy

What makes Merge Agent Handler's Expensify MCP server better than alternative Expensify MCP servers?

Here are just a few reasons:

• Enterprise-grade security and DLP. Merge Agent Handler lets you define data loss prevention rules that block or redact specific fields before they reach your agent. For Expensify, that means employee expense details, reimbursement amounts, and card numbers can be filtered out at the tool layer, even if the agent has broad read permissions

• Managed authentication and credentials. Merge stores your Expensify partner credentials and handles all token management. You never pass raw API keys to an agent or coordinate credential rotation when keys expire

• Real-time observability and audit trail. Each Expensify tool call is recorded with a full log: timestamp, tool name, parameters sent, and response received. Finance and compliance teams can review exactly what the agent accessed or modified, without any additional instrumentation

• Tool Packs and controlled access. Tool Packs let you scope an agent's access to only the Expensify tools it actually needs. A reconciliation agent gets export tools. An approval agent gets status update tools. Neither has access to tools outside its defined scope

How can I start using Merge Agent Handler's Expensify MCP server?

You can take the following steps:

1. Create your Merge Agent Handler account and navigate to Tool Packs.

2. Create a new Tool Pack, then find and enable the Expensify connector. Choose which tools to include — enable read tools for reporting and reconciliation workflows, or add write tools like create_expenses and update_report_status if your agent needs to create or modify data.

3. Add a Registered User inside the Tool Pack. This is the identity context under which your agent operates. Merge generates a unique MCP URL scoped to this user once it's created.

4. From the Registered User detail page, authenticate Expensify by completing the credential flow. Merge stores and manages the credentials going forward.

5. Copy the MCP URL from the Tool Pack detail page and generate an API key from Settings. You'll need both to connect your agent.

6. Add the MCP server to your agent or IDE using the MCP URL and API key. Your Expensify tools will now be accessible through that endpoint.