How do I install SAP SuccessFactors?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does SAP SuccessFactors need an API key?

No required environment variable is listed on this record.

What transport does SAP SuccessFactors use?

SAP SuccessFactors runs locally over stdio.

When was SAP SuccessFactors last checked?

Last checked 2026-11-10. SAP SuccessFactors OData and Compound Employee queries with PII tokenization for AI agents.

SAP SuccessFactors MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

docker run -i --rm docker.io/wudaoyou/successfactors-toolkit:v0.7.0

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add io.github.wudaoyou-successfactors-toolkit -- docker run -i --rm docker.io/wudaoyou/successfactors-toolkit:v0.7.0

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.wudaoyou-successfactors-toolkit": {4      "command": "docker",5      "args": [6        "run",7        "-i",8        "--rm",9        "docker.io/wudaoyou/successfactors-toolkit:v0.7.0"10      ]11    }12  }13}

claude_desktop_config.json

Local · ociPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 0.7.0
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

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.

API	Protocol	Endpoint prefix
EC SFAPI — Compound Employee	SOAP 1.1	`/api/sfapi/ce/`
OData	REST (v2, v4)	`/api/odata/`

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:

Check Docker Desktop or your IT-managed Docker service is running, then open your local AI application.

Confirm with IT that the connection files are in sf-toolkit/credentials/systems, one folder per SuccessFactors system.

Confirm which SuccessFactors system to use and ask for the employee, date, and information you need.

Find results under sf-toolkit/data/mcp. Ask a file-capable AI application for CSV or another supported format, or a copy in an authorized folder.

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

Page	Covers
REST API	Fail-closed setup, install and run, cheat sheet, response format
Connect to SuccessFactors	Key pair generation, system files (`SYSTEMS_DIR/<name>/<name>.json`), environment variables, system management
EC SFAPI (SOAP)	Compound Employee single lookup, structured filter query, pagination, known footguns
OData API	`execute` / `extract` / `extract-by-filter-in`, OData v4 services, per-request connection override, known API footguns
MCP server	Tools for AI agents, payload handling, export formats, PII tokenization, plugins
Development	Local dev setup, linting, tests, release process

Data handling

Use synthetic examples and test fixtures. Credentials, certificates, tenant exports, employee payloads, and generated results do not belong in Git — .gitignore and scripts/check_repository.py are a basic guardrail, not a complete secret or personal-data scanner. See SECURITY.md for deployment guidance and how to report a vulnerability.

License