SAP SuccessFactors

io.github.wudaoyou由 GitHub 账号 wudaoyou 发布v0.7.0更新于 Oct 24, 2026

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

概览

AI 生成的概览

一个自托管的 Docker MCP 服务器,让 AI 助手查询 SAP SuccessFactors 的 OData 与 Compound Employee 接口,并支持 PII 令牌化与本地导出。

可以做什么
通过 execute、extract 和按条件过滤等操作查询 SuccessFactors OData v2 与 v4 服务,支持按请求覆盖连接并处理已知接口陷阱。通过 SOAP 查询和筛选 Employee Central 的 Compound Employee 数据,包括分页。对载荷中的 PII 进行令牌化,并以 CSV 等支持的格式导出结果。将结果写入本地数据目录,便于查看或复制到授权文件夹。通过插件扩展功能。
适用场景
适合需要让 AI 助手排查 SuccessFactors 接口问题、提取员工数据或针对租户原型验证集成的功能顾问、业务关键用户和集成开发人员。尤其适用于 HR 数据必须留在受控本地机器的场景。
运行要求
需要运行中的 Docker Desktop 或 IT 托管的 Docker 服务,以 stdio 方式运行已发布的镜像。需要一次性 Docker Compose 配置和经批准的连接文件,凭据目录下每个 SuccessFactors 系统一个文件夹,并包含生成的密钥对。需要访问所配置 SuccessFactors 租户的网络。CSV 转换需要具备文件处理能力的 AI 应用。
安装前请注意
它会连接真实的 SuccessFactors 租户并查询真实员工数据。凭据、证书、租户导出和员工载荷不得进入 Git;仓库中的防护措施并非完整的密钥或个人信息扫描器。调用云端模型的本地代理可能把提示、工具响应和文件内容发送到本机之外,若 HR 数据必须留在受控环境,应使用本地托管的模型。优先选择本地部署而非托管 MCP 服务。

安装

在 SourceWeft 中

  1. 打开 控制台中的 SAP SuccessFactors,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

SuccessFactors Toolkit

[CI] [License] [Python]

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.

APIProtocolEndpoint prefix
EC SFAPI — Compound EmployeeSOAP 1.1/api/sfapi/ce/
ODataREST (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:

  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/systems, one folder per SuccessFactors system.
  3. Confirm which SuccessFactors system to use and ask for the employee, date, and information you need.
  4. 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

PageCovers
REST APIFail-closed setup, install and run, cheat sheet, response format
Connect to SuccessFactorsKey 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 APIexecute / extract / extract-by-filter-in, OData v4 services, per-request connection override, known API footguns
MCP serverTools for AI agents, payload handling, export formats, PII tokenization, plugins
DevelopmentLocal 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

Apache License 2.0. Copyright 2026 Justin Gong. See NOTICE for third-party and migrated-code attribution.

来源:README.md,提交 db32da4

工具

0
SourceWeft 曾在隔离沙箱中以无凭据方式启动该软件包一次,以列出其工具,但未能完成:该软件包类型无法在沙箱中运行。

版本历史

7
  1. v0.7.0最新Oct 24, 2026
  2. v0.6.0Oct 6, 2026
  3. v0.5.5Oct 3, 2026
  4. v0.5.4Oct 2, 2026
  5. v0.5.2Sep 30, 2026
  6. v0.5.0Sep 29, 2026
  7. v0.4.1Sep 29, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分