Skip the install. Get this working in under 2 minutes.
Start a free trial on cloud.anythingmcp.com, add the SAP SuccessFactors in one click, then point your AI client (Claude, ChatGPT, Copilot or Cursor) at the generated MCP endpoint. No Docker, no git clone, zero engineering experience required.
AnythingMCP is listed in Claude's connector directory: add it to Claude in one click (opens in a new tab), then sign in and choose which MCP servers Claude may use.
Summary
Read SAP SuccessFactors Employee Central through its OData API: employees, job information, persons, companies, departments, positions and time off, plus generic OData tools for any other entity. OAuth 2.0 SAML bearer, read-only.
Try asking
Example prompts for SAP SuccessFactors
Click any prompt to copy it. Paste into Claude, ChatGPT, Cursor, Gemini, Copilot or OpenClaw to run it against this connector.
Claude is AI and can make mistakes. Please double-check responses.
💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → SAP SuccessFactors, paste your credentials, mint an MCP API key and you're done. No Docker, no
git clone, no local server.
SAP SuccessFactors + Claude
Read SAP SuccessFactors Employee Central through its OData API: employees, job information, persons, companies, departments, positions and time off, plus generic OData tools for any other entity. OAuth 2.0 SAML bearer, read-only.
Prerequisites
See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:
SF_API_URL, SF_COMPANY_ID, SF_CLIENT_ID, SF_SAML_ASSERTION
Step 1 — Get credentials
- In SuccessFactors open Admin Center → Manage OAuth2 Client Applications → Register Client Application. Generate an X.509 certificate there (or upload your own), download the private key, and copy the API Key shown after registering into
SF_CLIENT_ID. - Generate a SAML assertion for the API user with SAP's offline SAML assertion generator (SAP Note 3031657): token URL
<api-server>/oauth/token, the API key as client id, the API user, the private key, andexpireInMinutesset to how long the assertion should stay usable. Paste the base64 assertion intoSF_SAML_ASSERTION. - Set
SF_API_URLto the OData API server of your data center, without/odata/v2, for examplehttps://api4.successfactors.comorhttps://api012.successfactors.eu. SAP's List of SAP SuccessFactors API Servers names it, and it matches the host of your login URL. - Set
SF_COMPANY_IDto your company ID: it is shown under your name (top right) → Show version information, and in the login URL ascompany=. - Give the API user the Employee Central API permission (Role-Based Permissions → Employee Central API: OData API access) and read permission on the entities and fields the AI should see.
- Install the connector. Start with
sap_successfactors_guide, which costs no API call, then runsap_successfactors_list_users: a list of employees shows the connection works.
Tokens: the connector exchanges the assertion for an access token valid 24 hours and renews it automatically while the assertion is valid. When the assertion expires, generate a new one and paste it into SF_SAML_ASSERTION. SAP retires HTTP Basic authentication for these APIs on 20 November 2026, so it is not offered.
Read-only: the AI reads, it does not change anything in SuccessFactors. Every call runs as the API user the assertion names, so SuccessFactors role-based permissions decide what it sees.
What it reads: employee profiles with their userId, job information (company, department, position, manager, employment status), person records with personal info, emails and phones, legal entities, departments, positions with vacancy and FTE, and time off requests. For any other entity, sap_successfactors_get_entity_metadata lists its fields and the generic OData tools read it.
Effective dating: job information, companies, departments and positions return the record valid today. Ask for a date or a date range when you need history.
Limits: a page holds at most 1000 rows, and the AI narrows large lists with filters. SAP throttles heavy API use per tenant, so the AI filters by last change date instead of reading all users again and again.
Good to know: inactive users only appear when you ask for them by status, and picklist fields come back as codes unless the AI expands their labels.
The connector does not hire, change job or pay data, approve time off or write to any SuccessFactors entity.
Step 2 — Install the adapter
curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d
Step 3 — Add the connector in Claude
Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (
https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide showsYOUR_SERVER_ID.
Recommended path: works on claude.ai web without editing any config file.
- In Claude, open Customize → Connectors.
- Click +, then Add custom connector.
- Enter a name, e.g.
SAP SuccessFactors, and the remote MCP server URLhttps://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID, then click Add. - Click Connect and sign in to AnythingMCP (OAuth) to allow access.
All tools below appear in your chat: start typing prompts.
Available tools
| Tool | What it does |
|---|---|
sap_successfactors_list_services | Where the SAP SuccessFactors OData service lives |
sap_successfactors_describe_service | The entity sets of a SAP SuccessFactors OData service with their business labels, keys and whether they are analytical (the server… |
sap_successfactors_describe_entity | The fields of one entity set: labels, types, keys, the currency or unit field of each amount, the text field of each code, dimensions and… |
sap_successfactors_query | Read rows from an entity set of SAP SuccessFactors |
sap_successfactors_get_entity | Read one entity of SAP SuccessFactors by its key, optionally with related entities |
sap_successfactors_guide | How to read SAP SuccessFactors through its OData API: the workflow, filter syntax, effective dating (asOfDate, fromDate, toDate), the… |
sap_successfactors_list_users | Employee profiles from the User entity: userId, username, name, email, department, division, location, title and status |
sap_successfactors_get_user | One employee profile from the User entity by userId, with optional select and expand (e.g. manager, hr, empInfo/jobInfoNav) |
sap_successfactors_list_employee_jobs | Job information (EmpJob, effective-dated): userId, startDate, company, business unit, division, department, location, position, job code… |
sap_successfactors_list_persons | Person records (PerPerson): personIdExternal, date and place of birth, with navigations to personal info (personalInfoNav), emails… |
sap_successfactors_list_companies | Legal entities (FOCompany, effective-dated): externalCode, name, country, currency, status and default location |
sap_successfactors_list_departments | Departments (FODepartment, effective-dated): externalCode, name, description, parent department, head of unit and cost center |
sap_successfactors_list_positions | Positions from Position Management (Position, effective-dated): code, externalName_defaultValue, company, department, job code, vacant… |
sap_successfactors_list_time_off | Time off and absence requests (EmployeeTime from Time Off): userId, timeType, startDate, endDate, quantityInDays or quantityInHours and… |
sap_successfactors_get_entity_metadata | The metadata of one entity (e.g |
Example prompts
- "How many active employees do we have per department, and who heads each department?"
- "Who is absent next week, and which time off requests are still waiting for approval?"
- "List our vacant positions with their company, department and FTE."
- "Show the job history of employee 10234 over the last two years: department, position and manager changes."
FAQ
Does it work with Claude Code as well as Claude Desktop? Yes, point both at https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.
Next steps
Was this guide helpful?