MCP.Market

SAP SuccessFactors MCP server

by wudaoyou·io.github.wudaoyou/successfactors-toolkit·v0.7.0·3 stars

SAP SuccessFactors OData and Compound Employee queries with PII tokenization for AI agents.

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

not scanned yet

Adoption
Growing

3 stars

Reviews

Write one

Nobody has reviewed SAP SuccessFactors yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

SAP SuccessFactors tools

No tool declarations could be read from the package source. They show once the server is installed.

Not scanned yet. New listings are scanned within a day or two of arriving.

How SAP SuccessFactors compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
88/100
higher than 75% of 48,255 servers
GitHub stars
3
more than 80% of 28,688 servers

Release history: 5 versions in the registry since 2026-09-29, latest 2026-10-24, typically one every 3 days.

Install SAP SuccessFactors in Claude Code, Cursor or VS Code

claude mcp add successfactors-toolkit -- docker run -i --rm docker.io/wudaoyou/successfactors-toolkit:v0.7.0
Add to Cursor

What the publisher says

From the SAP SuccessFactors repository's README, as published. We do not edit it. Read it on GitHub

SuccessFactors Toolkit

A self-hosted toolkit for SAP SuccessFactors API troubleshooting, payload extraction, and integration development, exposed as a REST API and as an MCP (Model Context Protocol) server.

OData v4 covers the SuccessFactors APIs published as v4 services (for example Calibration and Continuous Feedback); Employee Central and Onboarding data stay on v2. See OData API.

This is an independent project, not affiliated with or endorsed by SAP SE. SAP and SuccessFactors are trademarks of SAP SE.

Start here: Docker MCP → credentials → ask → export

Data security: prefer local deployment. For sensitive SuccessFactors

employee data and credentials, we recommend running the MCP server in local

Docker and using a local AI agent, rather than an online AI platform or a

third-party hosted MCP service. Keep credentials and exports on your machine;

do not upload private keys or employee payloads to online platforms.

A local AI agent is not necessarily a local model. If it calls a cloud

model, prompts, tool responses, previews, and file contents supplied to that

model may leave your machine. If HR data must stay within your controlled

environment, use a locally hosted model and local file-processing tools,

and check the agent's outbound data handling. Local Docker alone does not

guarantee this. The toolkit still connects to your configured SuccessFactors

tenant to query data.

For functional consultants and business key users, start with the business user guide or its English/Chinese HTML edition. Ask IT to complete the one-time Docker Compose setup and provide approved connection files. Then:

and information you need.

  1. Check Docker Desktop or your IT-managed Docker service is running, then open your local AI application.
  2. Confirm with IT that the connection files are in sf-toolkit/credentials.
  3. Confirm the SuccessFactors environment and ask for the employee, date,

for CSV or another supported format, or a copy in an authorized folder.

  1. Find results under sf-toolkit/data/mcp. Ask a file-capable AI application

The guide includes example business questions, completion checks, troubleshooting, and expandable one-time settings for your administrator. Original OData results are JSON; Compound Employee results are XML. CSV conversion requires local file tools in the AI application.

Documentation

Data handling

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

SAP SuccessFactors: common questions

Is SAP SuccessFactors MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the SAP SuccessFactors safety report
How do I install SAP SuccessFactors?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does SAP SuccessFactors need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is SAP SuccessFactors maintained?
The last commit was 34 days ago (2026-10-01). The latest release is v0.7.0.
How does SAP SuccessFactors compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,255 servers); github stars 3 (more than 80% of 28,688 servers). Full comparison.