Microsoft has MCP servers. Stripe has MCP servers. Now SAP has one. io.github.cap-js/mcp-server brings the Cloud Application Programming model — SAP's primary framework for building enterprise services — into the MCP registry at score 73.
What SAP CAP Is
SAP CAP (Cloud Application Programming model) is the framework developers use to build custom applications on SAP Business Technology Platform. It uses CDS (Core Data Services) for declarative data modeling and service definitions, with runtimes for both Node.js and Java. If a company runs SAP — and a staggering proportion of the Fortune 500 does — CAP is how their developers build extensions, integrations, and custom business applications on top of SAP's enterprise data layer.
The scale of the SAP ecosystem is easy to underestimate from the outside. SAP systems process 77% of the world's transaction revenue. CDS models define everything from purchase orders to supply chain logistics to HR workflows. The developers working in this ecosystem number in the hundreds of thousands, and they navigate a documentation surface that is vast, version-specific, and densely interconnected.
The MCP Integration
The MCP server means AI coding assistants can understand CAP data models, query CDS definitions, and help developers build SAP enterprise applications with accurate, context-aware guidance. This matters because SAP development has a steep learning curve — CDS syntax, OData service binding, HANA database artifacts, and platform-specific deployment configurations create a domain where even experienced developers spend significant time in documentation.
The cap-js GitHub organization is SAP's official home for CAP JavaScript tooling. This is not a community wrapper or a third-party integration — it is SAP's own team publishing an MCP server for their own framework. That distinction matters for trust. When a company the size of SAP decides the protocol is worth official support, it validates the ecosystem in a way that individual developer projects cannot.
The Numbers
| Metric | Value |
|---|---|
| Trust score | 73 |
| Stars | 87 |
| Forks | 14 |
| Watchers | 6 |
| License | Apache-2.0 |
| Active commit weeks | 14 |
| Contributors | 3 |
| Releases/year | 10 |
| Flags | None |
Clean sheet. No flags, no secrets required, code of conduct present. Apache-2.0 license. The 87 stars reflect early adoption within the SAP developer community — modest by open-source standards, substantial for enterprise framework tooling where adoption is driven by corporate mandates rather than GitHub trending pages.
The enterprise wave in MCP has been building quietly. Microsoft, Stripe, Sentry, and Datadog have all registered servers. SAP joining that list is significant because it represents a different kind of enterprise — not a developer-tools company adding AI features, but a traditional enterprise software giant deciding that AI coding assistants should understand its platform natively. If SAP's hundreds of thousands of developers start using MCP-connected assistants for CAP development, the protocol's footprint in enterprise software grows substantially overnight.
Score: 73. No flags. Apache-2.0.
Sources: cap-js — GitHub · Scorecard: io.github.cap-js (score 73)