# SAP Concur MCP connector

The SAP Concur connector brings travelers, trips, bookings, itineraries and meetings into Claude, ChatGPT, Cursor, Microsoft Copilot and any MCP client, so each person works on SAP Concur travel as themselves with every action logged.

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

## Facts

| | |
| --- | --- |
| Application | SAP Concur |
| Category | Accounting |
| AI tools | 380 |
| Authentication | Connects over OAuth |
| Bring your own OAuth app | Yes |
| 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 SAP Concur is connected

- Which itinerary trips depart next week, and who is traveling?
- Cancel Priya's booking to Berlin and note the reason.
- Create a SAP Concur user for the new hire starting Monday.

## Connect SAP Concur in Elaichi

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

1. Open Connections, choose Add connection, and pick SAP Concur.
2. Optionally set Share with, then press Connect.
3. Supply your own SAP Concur app, then approve. SAP Concur needs an OAuth app you register yourself, so bring its client ID and secret. One person does this once for the organization.

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

## SAP Concur 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.

## SAP Concur 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`.

## SAP Concur 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.

## SAP Concur 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.

## SAP Concur 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 SAP Concur 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 SAP Concur 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 SAP Concur through Elaichi

### See who is traveling next week

Travel. Ask for the itinerary trips departing in the next seven days and get the travelers, dates and destinations in one answer. Spot the overlap before the week starts.

### Book, change or cancel a trip

Executive assistants. Create a booking for the director's visit, add a trip extra when the hotel changes, and cancel the whole thing when the meeting moves. All from the chat window, all in SAP Concur.

### Set up a new hire in SAP Concur

HR. Create the SAP Concur user on their first day with the right details, then update it when they change team or manager. No admin screen to click through.

### Keep traveler profiles accurate

Finance. Search SAP Concur users for a cost center or approver that is out of date and fix the record in the same breath. Clean profiles mean clean travel reporting.

### Plan the meeting and its travel together

Events. Create the SAP Concur meeting, list who is already attending, and line up the trips around it. One conversation covers the event and the journeys to it.

### Update a batch of trips after a change

Operations. When a venue or date shifts, bulk update the affected legacy trips and cancel the ones that no longer make sense. Confirm the changes before anyone travels.

## Elaichi vs Zapier MCP vs Composio for SAP Concur

All three can connect SAP Concur 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 SAP Concur tools | Allow or restrict single SAP Concur 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 SAP Concur 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 SAP Concur to Claude?

Connect SAP Concur in Elaichi, then open Claude, go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. SAP Concur asks for an OAuth application registered in your own SAP Concur account, so an administrator brings its client ID and secret once when connecting, and nobody has to do that again. After that, each person signs in to SAP Concur as themselves.

### Does SAP Concur work with ChatGPT and Cursor as well as Claude?

Yes. SAP Concur is connected once in Elaichi and the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. Add it to a new client and SAP Concur is already there.

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

It can look up and update SAP Concur users, list and search trips and itineraries, create and cancel bookings, add or change trip extras, and create and read meetings. In practice that means asking who is traveling next week, booking a trip for a colleague, or setting up a new hire's SAP Concur profile. Short, concrete asks work better than long sentences.

### Does connecting SAP Concur give the AI every trip and every user?

No. Each person signs in to SAP Concur as themselves, so the agent only sees the trips, bookings and users that person could already see in SAP Concur. Elaichi can narrow that access further with roles and restrictions, and it never widens it.

### Can my team share one SAP Concur connection?

Yes. One administrator connects SAP Concur, shares the connection with a team, and nobody else ever handles the client ID or secret. Each person still signs in as themselves, so every trip booked or user updated is logged under their own name.

### Can I stop an agent from cancelling or changing things in SAP Concur?

Yes. Restrictions in Elaichi work per action, so you can allow reading trips while restricting cancelling bookings or updating SAP Concur users, and set that on a role or on one person. 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 a SAP Concur connection when someone leaves?

Offboarding that person in Elaichi ends their SAP Concur access at once, in every client. A shared SAP Concur connection keeps working for everyone else on the team. Disconnecting SAP Concur once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.

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

Yes. SAP Concur 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 SAP Concur?

Yes. Both let Claude, ChatGPT or Cursor use SAP Concur. 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 SAP Concur call.

### How is Elaichi different from Composio for SAP Concur?

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 SAP Concur: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

## All 380 SAP Concur tools

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

- **List all SAP Concur users** (List). List users. Retrieves all users of a given company. SAP Concur API (GET /profile/identity/v4.1/Users). OAuth scope: identity.user.ids.read, identity.user.core.read, identity.user.coresensitive.read, identity.user.enterprise.read. Paginated with cursor/count (max 1000).
- **Get single SAP Concur user by ID** (Get). Retrieve a user. Retrieves a unique user based on the user's UUID. SAP Concur API (GET /profile/identity/v4.1/Users/{id}). Required: user_id. OAuth scope: identity.user.ids.read, identity.user.core.read, identity.user.coresensitive.read, identity.user.enterprise.read.
- **SAP Concur users search** (Search). Search users. Retrieves matching user identity profiles based on one or more filter expressions; supports booleans, strings, numbers, dates and lists in the User schema. SAP Concur API (POST /profile/identity/v4.1/Users/.search). Required: schemas. OAuth scope: identity.user.ids.read, identity.user.core.read, identity.user.coresensitive.read, identity.user.enterprise.read. Returns one page; pass the paging token/parameters from the previous response to get the next page (cursor in request body (cursor) + count).
- **Create a SAP Concur user** (Create). Create a user. Creates a user's identity profile. SAP Concur API (POST /profile/identity/v4.1/Users). Required: schemas, userName, active, name, emails. OAuth scope: identity.user.coreenterprise.writeonly, identity.user.externalID.writeonly, identity.user.sap.writeonly, identity.user.emails.verified.writeonly.
- **Update a SAP Concur user by ID** (Update). Update a user. Updates single or multiple attributes of a user using SCIM PATCH operations (add, replace, remove). SAP Concur API (PATCH /profile/identity/v4.1/Users/{id}). The id is the id. Required: id, schemas, Operations. OAuth scope: identity.user.coreenterprise.writeonly, identity.user.externalID.writeonly, identity.user.sap.writeonly.
- **SAP Concur users replace** (Action). Replace a user. Replaces a user's identity profile; any data not included in the payload is removed (full replace). SAP Concur API (PUT /profile/identity/v4.1/Users/{id}). The id is the id. Required: id, schemas, userName, active, name, emails. OAuth scope: identity.user.coreenterprise.writeonly, identity.user.externalID.writeonly, identity.user.sap.writeonly, identity.user.emails.verified.writeonly.
- **Get single SAP Concur trips v 5 by ID** (Get). Retrieve a trip by ID. Returns the full trip record for a given trip UUID, including itinerary segments, booking details, traveler information, locations, and pricing. The response payload is filtered based on the granted scopes. SAP Concur API (GET /v5/trips/{tripID}). The id is the tripID. Required: id. OAuth scope: travel.trip.booking.read, travel.trip.location.read, travel.trip.pricing.read, travel.trip.read.
- **Get single SAP Concur itinerary trip by ID** (Get). Retrieve a trip by ID. Retrieves the record of a trip (itinerary) including bookings, segments, tickets and charges. SAP Concur API (GET /travel/v4/trips/{id}). The id is the id. Required: id. OAuth scope: travel.itinerary.read.
- **List all SAP Concur itinerary trips** (List). List trips. Retrieves a list of trips booked within the last 6 months (historical initial data fetch only; rate limited to 10 requests per minute). Returns at most 10 trips per page with next/prev operations. SAP Concur API (GET /travel/v4/trips). OAuth scope: travel.itinerary.read. Returns one page; pass the paging token/parameters from the previous response to get the next page (cursor: startAfter query; response 'operations' array contains rel=next/prev href URLs (max 10 items per page)).
- **Create a SAP Concur booking** (Create). Create or update a booking. Creates a new booking or updates an existing booking. The booking is assigned to the specified trip, or the first itinerary spanning the booking dates, or a new itinerary is created. Suppliers/TMCs with admin roles can act on behalf of another user. SAP Concur API (POST /api/travel/booking/v1.1). OAuth scope: ITINER. Returns XML.
- **SAP Concur bookings cancel** (Cancel). Cancel a booking. Cancels an existing booking. Can cancel bookings the OAuth consumer does not own when the caller (TMC) has the required admin role. Returns the full booking details; 404 if not found. SAP Concur API (POST /api/travel/booking/v1.1/cancel). Required: bookingSource, confirmationNumber. OAuth scope: ITINER. Returns XML.
- **List all SAP Concur legacy trips** (List). List trip summaries. Retrieves trip summaries for a single user (or all users with userid_value=ALL for admins). Not meant for company-wide extraction. SAP Concur API (GET /api/travel/trip/v1.1). OAuth scope: ITINER. Paginated with Page/ItemsPerPage. Returns XML.
- **SAP Concur legacy trips search** (Search). List trip summaries (POST). Same as Get Trip Summaries but parameters are sent in a JSON request body instead of the query string. SAP Concur API (POST /api/travel/trip/v1.1/GetTrips). OAuth scope: ITINER. Paginated with Page/ItemsPerPage. Returns XML.
- **Get single SAP Concur legacy trip by ID** (Get). Retrieve trip details. Gets details for the specified trip, including bookings and segments. Elements vary by booking type, requestor, and GDS. TMCs with admin roles can retrieve trips on behalf of users. SAP Concur API (GET /api/travel/trip/v1.1/{tripId}). The id is the tripId. Required: id. OAuth scope: ITINER. Returns XML.
- **Create a SAP Concur legacy trip** (Create). Create a trip. Creates a new trip. The dates in the body can only span the trip to be created and cannot span an existing trip. TMCs/suppliers with admin roles can create on behalf of a user. SAP Concur API (POST /api/travel/trip/v1.1). OAuth scope: ITINER. Returns XML.
- **SAP Concur legacy trips bulk update** (Update). Update a trip. Creates a new trip or updates an existing trip; if a tripId is included in the URI the specified trip is replaced with the full trip in the request. The section gives no explicit request line; URL taken from the tripid example in the Cancel section. SAP Concur API (POST /api/travel/trip/v1.1). Required: trip_id. OAuth scope: ITINER. Returns XML.
- **SAP Concur legacy trips cancel** (Cancel). Cancel a trip. Cancels all segments in a trip and returns the full trip details for the cancelled trip. SAP Concur API (POST /api/travel/trip/v1.1/cancel). OAuth scope: ITINER. Returns XML.
- **Create a SAP Concur trip extra** (Create). Append a trip extras booking. Appends extras booking content from an external partner to an existing trip. Returns 202 Accepted with the bookingUuid while processing. SAP Concur API (POST /travel/v5/trips/{trip_uuid}/trip-extras). Required: trip_uuid, extRef, userId, initiator, booking. OAuth scope: travel.trips.read, travel.trips.booking.write.
- **Update a SAP Concur trip extra by ID** (Update). Update a trip extras booking. Updates an existing extras booking on an existing trip. SAP Concur API (PUT /travel/v5/trips/{trip_uuid}/trip-extras/{booking_uuid}). The id is the booking_uuid. Required: id, trip_uuid, extRef, userId, initiator, booking. OAuth scope: travel.trips.read, travel.trips.booking.write.
- **SAP Concur trip extras cancel** (Cancel). Cancel a trip extras booking. Cancels the extras booking. Responds 204 No Content on success. SAP Concur API (POST /travel/v5/trips/{trip_uuid}/trip-extras/{booking_uuid}/cancel). Required: trip_uuid, booking_uuid, userId, initiator. OAuth scope: travel.trips.read, travel.trips.booking.write.
- **List all SAP Concur meetings** (List). List meetings. Retrieves meetings for the caller's company. SAP Concur API (GET /meetings/v4/meetings). Returns one page; pass the paging token/parameters from the previous response to get the next page (offset+limit query; response 'pagination' object {limit, offset, total}).
- **Create a SAP Concur meeting** (Create). Create a meeting. Creates a meeting in the caller's company; response includes the generated id and status. SAP Concur API (POST /meetings/v4/meetings). Required: companyId, name, locationName, airport, startDateTime, endDateTime, timeZone, travelConfigId.
- **Get single SAP Concur meeting by ID** (Get). Retrieve a meeting. Retrieves full meeting details including metadata, settings, and discounts. SAP Concur API (GET /meetings/v4/meetings/{meetingId}). The id is the meetingId. Required: id.
- **SAP Concur meetings get metadata** (Get). Retrieve meeting metadata. Read-only metadata sub-resource of a meeting, mentioned only in prose under Get a Meeting ("Related read-only sub-resources: GET /meetings/{meetingId}/metadata, /settings, /discounts, and /history"). Full path presumably https://{datacenterURI}/meetings/v4/meetings/{meetingId}/metadata. SAP Concur API (GET /meetings/v4/meetings/{meetingId}/metadata). Required: meeting_id.
- **SAP Concur meetings get settings** (Get). Retrieve meeting settings. Read-only settings sub-resource of a meeting, mentioned only in prose under Get a Meeting ("Related read-only sub-resources: GET /meetings/{meetingId}/metadata, /settings, /discounts, and /history"). Full path presumably https://{datacenterURI}/meetings/v4/meetings/{meetingId}/settings. SAP Concur API (GET /meetings/v4/meetings/{meetingId}/settings). Required: meeting_id.
- **SAP Concur meetings get discounts** (Get). Retrieve meeting discounts. Read-only discounts sub-resource of a meeting, mentioned only in prose under Get a Meeting ("Related read-only sub-resources: GET /meetings/{meetingId}/metadata, /settings, /discounts, and /history"). Full path presumably https://{datacenterURI}/meetings/v4/meetings/{meetingId}/discounts. SAP Concur API (GET /meetings/v4/meetings/{meetingId}/discounts). Required: meeting_id.
- **SAP Concur meetings get history** (Get). Retrieve meeting history. Read-only history sub-resource of a meeting, mentioned only in prose under Get a Meeting ("Related read-only sub-resources: GET /meetings/{meetingId}/metadata, /settings, /discounts, and /history"). Full path presumably https://{datacenterURI}/meetings/v4/meetings/{meetingId}/history. SAP Concur API (GET /meetings/v4/meetings/{meetingId}/history). Required: meeting_id.
- **Update a SAP Concur meeting by ID** (Update). Update a meeting. Partially updates a meeting using JSON Merge Patch. SAP Concur API (PATCH /meetings/v4/meetings/{meetingId}). The id is the meetingId. Required: id.
- **Delete a SAP Concur meeting by ID** (Delete). Delete a meeting. Soft-deletes the meeting. Returns 204. SAP Concur API (DELETE /meetings/v4/meetings/{meetingId}). The id is the meetingId. Required: id.
- **List all SAP Concur meeting attendees** (List). List attendees. Retrieves attendees for a meeting. SAP Concur API (GET /meetings/v4/meetings/{meetingId}/attendees). Required: meeting_id.
- **Create a SAP Concur meeting attendee** (Create). Add an attendee. Adds a single attendee to a meeting. SAP Concur API (POST /meetings/v4/meetings/{meetingId}/attendees). Required: meeting_id, email, firstName, lastName, profileType.
- **SAP Concur meeting attendees bulk create** (Create). Add attendees in bulk. Adds multiple attendees to a meeting. Returns 207 Multi-Status with per-item results. SAP Concur API (POST /meetings/v4/meetings/{meetingId}/attendees/bulk). Required: meeting_id, attendees.
- **Get single SAP Concur meeting attendee by ID** (Get). Retrieve an attendee. Retrieves a single attendee. SAP Concur API (GET /meetings/v4/meetings/{meetingId}/attendees/{attendeeId}). The id is the attendeeId. Required: id, meeting_id.
- **Update a SAP Concur meeting attendee by ID** (Update). Update an attendee. Partially updates an attendee using JSON Merge Patch. SAP Concur API (PATCH /meetings/v4/meetings/{meetingId}/attendees/{attendeeId}). The id is the attendeeId. Required: id, meeting_id.
- **Delete a SAP Concur meeting attendee by ID** (Delete). Delete an attendee. Removes an attendee from a meeting. SAP Concur API (DELETE /meetings/v4/meetings/{meetingId}/attendees/{attendeeId}). The id is the attendeeId. Required: id, meeting_id.
- **SAP Concur meeting attendees create login URL** (Create). Generate attendee login URL. Generates a one-time login URL for a non-employee attendee. SAP Concur API (POST /meetings/v4/meetings/{meetingId}/attendees/{attendeeId}/login-url). Required: meeting_id, attendee_id.
- **Get single SAP Concur meeting form datum by ID** (Get). Retrieve company form data. Retrieves the travel configs and their rule classes for a company, used to populate options when creating or editing a meeting. SAP Concur API (GET /meetings/v4/companies/{companyId}/form-data). Required: company_id.
- **SAP Concur travel profile loyalty bulk update** (Update). Update loyalty program information. Updates the loyalty program membership information for the OAuth consumer. Travel suppliers can update only their own program; TMCs can update any loyalty program for the user. Available only to suppliers who completed the app review process. SAP Concur API (POST /api/travelprofile/v1.0/loyalty). Returns XML.
- **Get single SAP Concur travel profile by ID** (Get). Retrieve a travel profile. Provides travel profile information for the specified user (or the token's user), including identity, contact information, rate preferences, discount codes, travel-type preferences and custom fields. SAP Concur API (GET /api/travelprofile/v2.0/profile). Returns XML.
- **SAP Concur travel profiles upsert** (Upsert). Create or update a travel profile. Creates or updates a travel profile using the same XML model as the GET response (ProfileResponse root with Action="Create"|"Update" and LoginId attributes). Omitted elements are ignored; empty string elements are cleared. SAP Concur API (POST /api/travelprofile/v2.0/profile). Returns XML.
- **List all SAP Concur travel profile summaries** (List). List travel profile summaries. Provides a paged list of travel profile summaries updated since the specified date. SAP Concur API (GET /api/travelprofile/v2.0/summary). Required: LastModifiedDate. Paginated with Page/ItemsPerPage. Returns XML.
- **List all SAP Concur travel receipt requests** (List). List travel receipt requests. Retrieves all travel receipt requests for the e-receipt partner, telling partners which e-receipts to send and for which user. Without a timestamp, results from the last 24 hours are returned; max 25 per page. SAP Concur API (GET /travelreceipts/v1/receiptrequests/{ts}/{key}). Required: ts, key. OAuth scope: travel.receipts.read. Returns one page; pass the paging token/parameters from the previous response to get the next page (cursor: response 'next' field holds path /v1/receiptrequests/{ts}/{key} for next page (25 per page); last page when next is null/empty).
- **Get single SAP Concur travel allowance calculation result by ID** (Get). Retrieve travel allowance calculation results. Returns the detailed travel allowance calculation results (client and government amounts) for all itineraries assigned to the given expense report or travel request. SAP Concur API (GET /travelallowance/v4/users/{userId}/contexts/{context}/{contextId}/calculationresultdetails). Required: user_id, context, context_id. OAuth scope: travelallowance.itineraryresult.read.
- **List all SAP Concur travel allowance configuration summaries** (List). List travel allowance configuration summaries. Returns a summary of all configuration data needed to display travel allowance itinerary data (enabled fields, UI texts for labels and code values), translated per the Accept-Language header when available. SAP Concur API (GET /travelallowance/v4/configurationsummaries). OAuth scope: travelallowance.configuration.read. Returns one page; pass the paging token/parameters from the previous response to get the next page (cursor: pageId query; response links[rel=next].href).
- **Create a SAP Concur travel allowance itinerary** (Create). Create a travel allowance itinerary. Creates an itinerary for a user based on its configuration and itinerary segments. Response includes an Etag header. SAP Concur API (POST /travelallowance/v4/users/{userId}/itineraries). Required: user_id. OAuth scope: travelallowance.itinerary.writeonly.
- **List all SAP Concur travel allowance itineraries** (List). List travel allowance itineraries. Returns the itineraries of a user including header information (configuration, overlap type, trip type codes) and itinerary segments. SAP Concur API (GET /travelallowance/v4/users/{userId}/itineraries). Required: user_id. OAuth scope: travelallowance.itinerary.read. Returns one page; pass the paging token/parameters from the previous response to get the next page (cursor: pageId query; response links[rel=next].href).
- **Get single SAP Concur travel allowance itinerary by ID** (Get). Retrieve a travel allowance itinerary. Returns a specific itinerary of a user with header information and segments. Response includes an Etag header. SAP Concur API (GET /travelallowance/v4/users/{userId}/itineraries/{itineraryId}). The id is the itineraryId. Required: id, user_id. OAuth scope: travelallowance.itinerary.read.
- **Update a SAP Concur travel allowance itinerary by ID** (Update). Update a travel allowance itinerary. Updates an itinerary for a user. SAP Concur API (PUT /travelallowance/v4/users/{userId}/itineraries/{itineraryId}). The id is the itineraryId. Required: id, user_id. OAuth scope: travelallowance.itinerary.writeonly.
- **SAP Concur travel allowance itineraries simulate** (Action). Simulate a travel allowance itinerary. Returns the detailed calculation results (client and government amounts) for a simulated itinerary. SAP Concur API (POST /travelallowance/v4/users/{userId}/itinerarySimulation). Required: user_id. OAuth scope: travelallowance.itinerary.read.
- **Delete a SAP Concur travel allowance itinerary by ID** (Delete). Delete a travel allowance itinerary. Deletes an itinerary for a user. Returns 204 No Content. SAP Concur API (DELETE /travelallowance/v4/users/{userId}/itineraries/{itineraryId}). The id is the itineraryId. Required: id, user_id. OAuth scope: travelallowance.itinerary.writeonly.
- ...and 330 more tools. Call `tools/list` via the MCP endpoint, or see the full catalog via the API, for the complete set.
