SAP Concur MCP server
SAP Concur is the leading platform for corporate travel booking, expense reporting, and invoice management. Through the AI Gateway integration, an AI agent can create and submit expense reports, manage travel requests, process receipts, and handle approval workflows on your behalf. Finance teams, employees managing business travel, and administrators overseeing corporate spend will find this integration most useful.
Setting up an MCP server
This article covers the standard steps for creating an MCP server in AI Gateway and connecting it to an AI client. The steps are the same for every integration — application-specific details (API credentials, OAuth endpoints, and scopes) are covered in the individual application pages.
Before you begin
You'll need:
- Access to AI Gateway with permission to create MCP servers
- API credentials for the application you're connecting (see the relevant application page for what to collect)
Create an MCP server
Find the API in the catalog
- Sign in to AI Gateway and select MCP Servers from the left navigation.
- Select New MCP Server.
- Search for the application you want to connect, then select it from the catalog.
Configure the server
- Enter a Name for your server — something descriptive that identifies both the application and its purpose (for example, "Zendesk Support — Prod").
- Enter a Description so your team knows what the server is for.
- Set the Timeout value. 30 seconds works for most APIs; increase to 60 seconds for APIs that return large payloads.
- Toggle Production mode on if this server will be used in a live workflow.
- Select Next.
Configure authentication
Enter the authentication details for the application. This varies by service — see the Authentication section of the relevant application page for the specific credentials, OAuth URLs, and scopes to use.
Configure security
- Set any Rate limits appropriate for your use case and the API's own limits.
- Enable Logging if you want AI Gateway to record requests and responses for auditing.
- Select Next.
Deploy
Review the summary, then select Deploy. AI Gateway provisions the server and provides a server URL you'll use when configuring your AI client.
Connect to an AI client
Once your server is deployed, you'll need to add it to the AI client your team uses. Select your client for setup instructions:
Tips
- You can create multiple MCP servers for the same application — for example, a read-only server for reporting agents and a read-write server for automation workflows.
- If you're unsure which OAuth scopes to request, start with the minimum read-only set and add write scopes only when needed. Most application pages include scope recommendations.
- You can edit a server's name, description, timeout, and security settings after deployment without redeploying.
Authentication
SAP Concur uses OAuth 2.0. To connect, you need a Client ID, Client Secret, and Company UUID from a registered OAuth app in the Concur Partner Portal. Configure the scopes appropriate for your use case — common ones include expense.report.readwrite, travel.request.read, and receipts.read.
Available tools
The integration covers the full expense lifecycle — from submitting a report to matching receipts and reconciling corporate card charges — as well as travel requests and supporting reference data.
Expense reports
| Tool | Description |
|---|---|
| Create report | Start a new expense report |
| Submit report | Submit a report for manager approval |
| Get report details | Retrieve the full content of a specific report |
| List reports | Return all reports for a user or team |
Expense entries
| Tool | Description |
|---|---|
| Create entry | Add an individual expense line to a report |
| Update entry | Edit an existing expense entry |
| Delete entry | Remove an entry from a report |
| Itemize expense | Split a single expense across multiple categories |
Receipts
| Tool | Description |
|---|---|
| Upload image | Attach a receipt image to the system |
| Get receipt | Retrieve a stored receipt |
| Match receipt | Associate a receipt with an expense entry |
| OCR data | Extract structured data from a receipt image |
Travel requests
| Tool | Description |
|---|---|
| Create request | Submit a pre-trip travel request |
| Get approval | Check the approval status of a request |
| Update request | Modify an existing travel request |
| Cancel request | Withdraw a submitted request |
Itineraries
| Tool | Description |
|---|---|
| Get trips | List upcoming and historical trips |
| Book travel | Create a travel booking |
| Update bookings | Modify an existing booking |
| Share itinerary | Send itinerary details to others |
User profile
| Tool | Description |
|---|---|
| Get user info | Retrieve a user's profile and preferences |
| Update profile | Modify user details |
| Manage delegates | Add or remove approval delegates |
| Set preferences | Configure notification and display settings |
Reference data
| Tool | Description |
|---|---|
| Expense types | Return the list of valid expense categories |
| Payment types | Return available payment method options |
| Vendors | Look up vendor records |
| Locations | Return valid location values for expense entries |
Tips
Use the minimum OAuth scopes needed for your use case — read-only scopes are sufficient for reporting workflows that don't create or modify data.
Validate expense types and payment types against the reference data tools before creating entries to avoid submission errors.
Include a business purpose in expense descriptions — many policies require it for approval, and the agent can prompt for it during report creation.
Cequence AI Gateway