NewSAP SuccessFactors, the HR suite
In the last 90 days
Change
Kind
Origin
Domain
8 changes
Agent access to your systemsdescription revisedKeep the default capability wording neutral; preserve the previous wording in framing_by_ecosystem.cap. Maintainer-requested scope audit.
Agent access to your systemscore coverage, coverage by ecosystem, description revisedMaintainer requested complementary boundaries so a CAP bridge can connect system access and application MCP exposure, while implementation restrictions remain explicit. Domains, providers and task classifications are unchanged.
Agent access to your systemsentry revisedSplit out of MCP servers at the maintainer's decision. That capability named a protocol and carried two concerns: exposing what you built to agents, which stays there under a name that says so, and giving agents a way into an SAP system you run, which is this one. Thirty providers moved with their own sentences; the Commerce and SuccessFactors slots moved with them. Named beside agent access to your code, its development-time sibling.
SF-MCPecosystem, provides revisedThe concern it answers is reaching into an SAP system from outside, split out of MCP servers on this day; the sentence on the edge is unchanged.
Show 2 more
SF-MCPadded to the atlasMCP server with 62 tools over SAP SuccessFactors OData APIs
SF-MCPentry revisedTriaged out of data/crawled/mcp-candidates.json, the sap-ai-mcp-servers sweep. Written from the repository's own README. Filed on the BTP door because there is no door for the SAP product it fronts and hard rule 9 allows one — the same strain recorded on the LeanIX entries.
Under no capability
aiadiguru2025first recorded in the atlas
Shakti Barathfirst recorded in the atlas
