Connect your AI Agents to Concur in minutes

What is a Concur MCP?

It's an MCP server that gives your agents access to SAP Concur expense management data and functionality through tools. Your agents can invoke these tools to retrieve and submit expense reports, upload receipts, approve or send back reports, manage quick expenses, and more.

SAP doesn't offer an MCP server purpose built for Concur, but you can use one from a third-party platform, like Merge Agent Handler.

How can I use the Concur MCP server?

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

• Automated expense report creation: When an employee books travel through a third-party tool, an agent creates a Concur report, adds the relevant expense line items, attaches receipt images, and submits the report for approval, removing the manual filing step entirely

• Approval queue management: A manager's AI monitors the list_reports_to_approve queue each morning, surfaces any reports that exceed policy thresholds, and drafts a summary for the manager to review before approving or sending back with comments

• Month-end spend reconciliation: On a scheduled cadence, an agent exports all submitted reports for a given period, cross-references expense amounts against budget data in a finance system, and flags any categories over threshold for the accounting team

• Receipt digitization workflow: When a receipt image lands in a shared inbox, an agent uploads it to Concur via upload_receipt_image_only, associates it with the matching expense line, and notifies the employee that the receipt has been attached

What are popular tools for Concur's MCP server?

Here are some of the most commonly used tools:

• list_reports: retrieves expense reports filtered by status, date range, or employee. Call this when an agent needs a current view of submitted or pending reports before generating a summary or triggering downstream actions

• create_report: opens a new expense report in Concur with a specified name and policy. Use this when an agent needs to group a set of expenses under a fresh report before submitting for approval

• create_report_expense: adds an expense line item to an existing report with amount, category, and date. Helpful when an agent is logging expenses automatically based on external events like bookings or card transactions

• submit_report: advances a report into the approval workflow. Good for workflows that complete all expense entry automatically and need to hand the report off to a manager without human intervention

• approve_report: approves a report that is pending manager or auditor sign-off. Use this when an agent validates expenses against policy and determines the report meets all criteria for approval

• upload_receipt: attaches a receipt file to an existing expense entry. Useful for agents that process inbound receipt images and need to associate them with the correct expense line in a report

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

A few things distinguish Merge Agent Handler's Concur MCP server from building your own or using a standalone alternative:

• Enterprise-grade security and DLP: Merge Agent Handler includes built-in data loss prevention controls that let you block or redact sensitive fields before they reach an agent. For Concur, this means expense amounts, employee reimbursement data, and corporate card details can be filtered at the tool layer even when the agent has broad read access

• Managed authentication and credentials: Merge stores your Concur OAuth credentials and manages token refresh on your behalf. You never expose raw API tokens to an agent or handle re-authentication when sessions expire

• Real-time observability and audit trail: Every Concur tool call is logged with timestamp, tool name, input parameters, and response metadata. Finance and compliance teams can audit exactly what an agent read, submitted, or approved without any additional instrumentation

• Tool Packs and controlled access: Tool Packs let you assemble the specific Concur tools an agent needs alongside tools from other connectors, all in one scoped endpoint. A reconciliation agent gets read access to reports and receipts. An approval agent gets submit and approve tools. Neither has access to operations outside its defined scope

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

You can take the following steps (assuming you use Claude Code):

1. Create or log into your Merge Agent Handler account.

2. Install the Merge CLI by running pipx install merge-api, then run merge configure to link the CLI to your Merge account and merge login to authenticate your session.

3. Register the Agent Handler MCP server with Claude Code by running claude mcp add --transport http agent-handler https://ah-api.merge.dev/mcp, then open Claude Code and run /mcp to confirm agent-handler appears with a connected status.

4. Select agent-handler from the MCP list. This opens a browser window where you select which integrations to authenticate. Choose Concur and complete the OAuth flow. Merge stores and manages the credentials going forward.

5. Open a Claude Code session and start querying Concur data directly. The first time you use a Concur tool, a Magic Link may appear to complete connector authentication.

If you want to connect Merge Agent Handler's Concur MCP with internal or customer-facing agentic products, you can follow the steps in our docs.

Can employees use Merge Agent Handler to connect their AI tools to Concur?

Yes, Agent Handler for Employees lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, Codex, and other MCP-compatible AI tools to Concur without bypassing IT governance.

Instead of setting up direct connections with personal credentials that IT can't monitor or revoke, each employee authenticates through Agent Handler and gets individual credentials tied to their identity. A finance analyst can ask their AI to pull submitted reports, flag over-budget categories, or retrieve pending approvals, all within the permissions IT has defined.

IT also provisions access by role or group via SCIM. A finance manager, for example, gets Concur access to review and approve expense reports, NetSuite to reconcile submitted spend against budget lines, and Slack to coordinate with employees on outstanding submissions; while a field sales rep gets Concur access to submit and track travel expenses, Salesforce to log client meetings and trips, and Gmail to manage receipts and reimbursement correspondence.

Every tool call an employee's AI makes to Concur is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.