SuccessFactors MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SF_API_URL | Yes | The base URL for the SAP SuccessFactors OData API | |
| SF_PASSWORD | Yes | Your SuccessFactors password | |
| SF_USERNAME | Yes | Your SuccessFactors username |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_user_dataA | Retrieve employee/user data from SuccessFactors. Returns specified fields for a user by USERID, EMPID, or EMAIL. |
| search_user_by_emailA | Search users by email and return basic identity info (userId, firstName, lastName, email). |
| post_user_dataB | Update or create employee/user data in SuccessFactors. Note: Creating new users may require additional permissions. |
| get_user_statisticsA | Get aggregate statistics about all users in SuccessFactors (total count, active users, etc.) |
| get_manager_hrB | Retrieve manager and/or HR information for a specific user in SuccessFactors. |
| update_manager_hrB | Update manager and/or HR assignment for a user in SuccessFactors. |
| manage_user_fieldsC | Get or update all standard user fields in SuccessFactors. Supports all 47 standard fields including STATUS, USERID, USERNAME, FIRSTNAME, LASTNAME, MI, GENDER, EMAIL, MANAGER, HR, DEPARTMENT, JOBCODE, DIVISION, LOCATION, TIMEZONE, HIREDATE, EMPID, TITLE, BIZ_PHONE, FAX, ADDR1, ADDR2, CITY, STATE, ZIP, COUNTRY, REVIEW_FREQ, LAST_REVIEW_DATE, CUSTOM01-CUSTOM15, MATRIX_MANAGER, DEFAULT_LOCALE, PROXY, CUSTOM_MANAGER, SECOND_MANAGER, LOGIN_METHOD, PERSON_GUID, and PERSON_ID_EXTERNAL. |
| get_complete_employee_dataA | Retrieve complete employee data with all fields and navigation properties (personKeyNav, manager, hr, empInfo, etc.). Returns the full OData entry as returned by SuccessFactors API, similar to fetching User('empId') with all expansions. |
| update_user_odataA | Update user data using PUT request with exact OData format. Accepts fields in camelCase format (matching SuccessFactors API format) such as firstName, lastName, email, status, timeZone, etc. Manager and HR should be provided as User IDs or "NO_MANAGER"/"NO_HR". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 9 tools
Several tools overlap in purpose: get_user_data, get_complete_employee_data, and search_user_by_email all retrieve user information at different levels, while post_user_data, manage_user_fields, and update_user_odata all provide ways to create or update user records. The descriptions clarify some boundaries, but an agent would struggle to confidently choose among these overlapping options.
Tool names mostly follow a consistent verb_noun pattern in snake_case (update_manager_hr, get_user_data, search_user_by_email). Minor deviations like post_user_data and manage_user_fields break the get/update pattern but the overall style remains predictable.
Nine tools is a reasonable count for a SuccessFactors user-management server and stays within the well-scoped range. The count is slightly high because several tools cover similar operations, so not every tool is clearly indispensable.
The set covers core user lifecycle operations: retrieval, lookup by email, statistics, and multiple update paths including manager/HR changes. It lacks explicit delete/list operations, but for an HR system those are often handled via status updates, so agents can work around the minor gaps.