SAP SuccessFactors MCP connector
The SAP SuccessFactors connector brings employee records, jobs, compensation, terminations and org structure into Elaichi, so Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent can answer questions from them inside each person's own SAP SuccessFactors access.
- Connects with an API key
- Free 14-day trial
- No credit card
Claude
Elaichi connected
List everyone who joined the Berlin location this month with job codes
Working in SAP SuccessFactors with Elaichi
-
List all SAP SuccessFactors odata per persons
-
-
Governance
/
Audit log
Last 24 hours
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
Claude · 9:41 AM
Done
ChatGPT · 9:38 AM
Done
Cursor · 9:35 AM
Done
How to connect SAP SuccessFactors to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
SAP SuccessFactors 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 SuccessFactors 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 SuccessFactors 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 SuccessFactors 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 SuccessFactors 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 SuccessFactors 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 SuccessFactors 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 SuccessFactors is logged.
-
HR
Answer a headcount question before the meeting
Ask how many people sit in a department, division or location today and get the number from live SAP SuccessFactors employment records, not last month's spreadsheet.
-
People Ops
Pull the new joiner list every Monday
List everyone whose employment started this month, with their job code, department and manager relationship, ready to paste into the onboarding plan.
-
Payroll
Check compensation before the pay run
Look up recurring and one-off pay components for a pay group and spot anything that changed since the last cycle.
-
Finance
Map people to cost centers for the forecast
Get every active employment grouped by cost center, company and business unit so the headcount budget matches what SAP SuccessFactors actually holds.
-
IT
Reconcile leavers against system access
List employment terminations from the past two weeks and compare them with who still has accounts, so offboarding does not lag behind.
-
Managers
Find a report's emergency contact fast
When something happens, ask for an employee's emergency contacts, phone numbers and work location and get them in seconds without opening SAP SuccessFactors.
Try asking
- “List everyone who joined the Berlin location this month with job codes”
- “Which employment terminations happened in March, grouped by department?”
- “Show emergency contacts and phones for employees in cost center 4100”
What connecting SAP SuccessFactors gets you
6 screens from Elaichi, each doing one job for your SAP SuccessFactors account.
Ask Elaichi to work across your apps.
List everyone who joined the Berlin location this month with job codes
Which employment terminations happened in March, grouped by department?
Show emergency contacts and phones for employees in cost center 4100
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about headcount, get today's answer.
Three prompts, live persons, jobs and departments from SAP SuccessFactors, answered in plain language.
ElaichiAI appsClaude
ChatGPT
Cursor
Microsoft Copilot
Copy the endpoint
AI apps
One endpoint, every client, no shared key.
Claude, ChatGPT, Cursor and Microsoft Copilot reach SAP SuccessFactors through one governed endpoint, each person signed in.
ElaichiToolsTool catalog
65 SAP SuccessFactors tools, zero code written.
Persons, employments, compensation and org foundation objects, covered without an engineer building anything.
ElaichiToolboxesToolboxes
Each team gets its own SAP SuccessFactors toolbox.
HR sees compensation, managers see jobs and departments, IT sees locations and cost centers.
ElaichiConnectionsShared connections
Teammates work through it, never see the key.
One person connects SAP SuccessFactors and shares it with teams, nobody else touches the API key.
ElaichiAudit logAudit log
Every lookup, named, timestamped, kept for good.
Who read which SAP SuccessFactors employment or compensation record, when, in one 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 SuccessFactors digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch persons
SAP SuccessFactors
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 SuccessFactors
Queued
Workflows
A schedule starts the work, a person approves.
Monday fires, new hires and terminations are fetched, grouped, drafted, approved, then sent on.
SAP SuccessFactors health
Refreshed 4 minutes ago · every 15 minutes · from the persons collection
Persons
1,284 ↓ 12%
Employments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Persons created
Last 14 days
By team
Share of activity
HR EMEA 34%
HR Americas 27%
Payroll 21%
Finance 18%
Collections and dashboards
Headcount numbers refresh themselves, nobody asks.
Four metrics, 14 days of employments created, a team breakdown, computed without a model.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for SAP SuccessFactors
All three can connect SAP SuccessFactors 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 SuccessFactors tools | Allow or restrict single SAP SuccessFactors 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 SuccessFactors 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 SuccessFactors tools for your AI agents
65 tools are ready to call through Elaichi's MCP endpoint the moment you connect SAP SuccessFactors, governed by the same roles, restrictions, and audit log as everything else in Elaichi.
No tools match your search.
Questions, answered
How do I connect SAP SuccessFactors to Claude?
Connect SAP SuccessFactors in Elaichi by pasting in an API key from your SAP SuccessFactors account; there is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and Claude can start answering questions from your SAP SuccessFactors records.
Does SAP SuccessFactors work with ChatGPT and Cursor as well as Claude?
Yes. Once SAP SuccessFactors is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any other MCP client and the Elaichi Agent. You connect SAP SuccessFactors once and every client picks it up.
What can an AI agent actually do with my SAP SuccessFactors data?
An agent can look up people, their emails, phones, addresses, national IDs and emergency contacts, and read their employments, jobs, compensation, pay components and terminations in SAP SuccessFactors. It can also read the org structure: companies, locations, departments, divisions, business units, cost centers, pay groups, job codes and job functions. Short, concrete asks such as "list terminations in March by department" work better than long sentences.
Does connecting SAP SuccessFactors give the AI access to everyone's records?
No. Every call to SAP SuccessFactors runs inside the access of the person who signed in, so the agent sees the same employees, compensation and org data that person could already open. Elaichi can narrow that further with roles and restrictions, and it can never widen it beyond what SAP SuccessFactors already allows.
Can I stop an agent from deleting or changing things in SAP SuccessFactors?
This SAP SuccessFactors connector reads records; it does not change or delete anything. Even so, Elaichi restrictions work per action, so you can switch off any lookup, such as compensation or national IDs, for a role. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor or Microsoft Copilot cannot run it, whatever the prompt says.
What happens to a SAP SuccessFactors connection when someone leaves?
Offboarding a person in Elaichi ends their access to SAP SuccessFactors through every client at once. A shared SAP SuccessFactors connection keeps working for everyone else on the team. If you want it gone entirely, disconnecting SAP SuccessFactors once in Elaichi removes it from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the SAP SuccessFactors MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. SAP SuccessFactors 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 SuccessFactors?
Yes. Both let Claude, ChatGPT or Cursor use SAP SuccessFactors. 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 SuccessFactors call.
How is Elaichi different from Composio for SAP SuccessFactors?
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 SuccessFactors: 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 SuccessFactors 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