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.
- Connects over OAuth
- Free 14-day trial
- No credit card
Which itinerary trips depart next week, and who is traveling?
Working in SAP Concur with Elaichi
-
List all SAP Concur users
-
Get single SAP Concur user by ID
-
SAP Concur users search
How to connect SAP Concur to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
SAP Concur MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ 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
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
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
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
3
Reload Cursor, then sign in and approve.
~/.cursor/mcp.json
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
Set up per machine, so repeat it on each computer you work from.
SAP Concur MCP connector for Microsoft Copilot
-
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.
https://api.elaichi.ai/mcp -
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.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
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
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
2
Sign in and approve.
{
"mcpServers": {
"elaichi": {
"url": "https://api.elaichi.ai/mcp"
}
}
}
The Elaichi Agent already has these tools, with nothing to set up.
What teams do with SAP Concur through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in SAP Concur is logged.
-
Travel
See who is traveling next week
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.
-
Executive assistants
Book, change or cancel a trip
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.
-
HR
Set up a new hire in SAP Concur
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.
-
Finance
Keep traveler profiles accurate
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.
-
Events
Plan the meeting and its travel together
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.
-
Operations
Update a batch of trips after a change
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.
Try asking
- “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.”
What connecting SAP Concur gets you
6 screens from Elaichi, each doing one job for your SAP Concur account.
Ask Elaichi to work across your apps.
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.
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about trips, get answers from live itineraries.
Type a question in plain language and the agent reads SAP Concur trips, bookings and users.
Copy the endpoint
AI apps
One endpoint brings SAP Concur to every client.
Claude, ChatGPT and Cursor reach SAP Concur through one governed endpoint, no SDK, no shared key.
Tool catalog
380 SAP Concur tools, no custom code required.
Users, trips, bookings, itineraries and meetings are covered without anyone writing a line.
Toolboxes
Every team gets its own SAP Concur toolbox.
Travel books trips, HR manages users, Events plans meetings, each from a toolbox scoped to them.
Shared connections
Share one SAP Concur connection, keep the secret.
One person connects, teammates book and update trips, nobody else ever sees a credential.
Audit log
Know who touched every SAP Concur trip.
When, who, what happened and which trip or user, in an append-only log.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
SAP Concur digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch users
SAP Concur
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
SAP Concur
Queued
Workflows
A schedule starts the work, you approve it.
Upcoming trips are fetched, grouped, drafted into a digest, approved, then posted back to SAP Concur.
SAP Concur health
Refreshed 4 minutes ago · every 15 minutes · from the users collection
Users
1,284 ↓ 12%
Trips
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Users created
Last 14 days
By team
Share of activity
Travel desk 34%
Executive office 27%
People ops 21%
Finance 18%
Collections and dashboards
SAP Concur health, computed, never asked for.
Numbers pulled from SAP Concur and computed, no model in the reporting, refreshed on schedule.
For IT and engineering
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.
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, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
SAP Concur tools for your AI agents
380 tools are ready to call through Elaichi's MCP endpoint the moment you connect SAP Concur, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Showing 179 of 380 SAP Concur tools here. Connect SAP Concur and call search_tools or tools/list over the MCP endpoint for the complete set.
Questions, answered
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 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.
Put SAP Concur in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot