Everything in CAP
Type: 2
Domain
Origin
Signals
More
Group by: Type
MCP server for CAP development: model and docs search
The tools are documented as meant for AI models and not a stable API, so anything built to parse `cds-mcp` output rather than to feed a model can break between releases. Its corpus is the CAP documentation, so Fiori elements, BTP service or ABAP questions are not in what `search_docs` indexes.
MCP server exposing the ODATANO Cardano-to-OData bridge as tools
The repository the package declares has been deleted — verified against the GitHub API, not just a failed fetch. The package is still on npm, so it installs; the source it was published from is no longer readable, which is a harder thing to discover than a stale version number.
MCP server exposing the NIGHTGATE Midnight attestation layer
MCP server for creating and editing Fiori applications
MCP server answering plain-English questions against a CDS schema
MCP server for UI5 development with ten tools
It reads a UI5 project and the framework's own documentation, not a running system or a backend: a question about the service behind the app is answered somewhere else. Node.js v20.17 or v22.9 and above.
MCP server generating tools from a CAP or OData V4 service's metadata
MCP server scaffolding CAP and CDS checked by cds compile
MCP server searching seventeen SAP documentation repositories
It reads documentation, never a system: nothing in it opens a package.json, a CDS model or an ABAP client, so a question about what your own project does has to be answered elsewhere. The offline half is only as fresh as the submodules the last build pinned, and the index answers where something is written down rather than which of two packages fits a task.
Hosted MCP server of developers.sap.com tutorials and missions
API proxies with security and traffic policies and Developer Hub
Identity Authentication and Identity Provisioning as one tenant
Managed queues and topics over AMQP, MQTT and REST
Joule's generative AI inside SAP Build Code
Low-code SAP Build capability for custom Joule skills and agents
Binding onto hyperscaler object storage, chosen by plan
Managed PostgreSQL from the hyperscaler via a BTP service binding
Managed Redis from the hyperscaler via a BTP service binding
AI runtime on BTP with the Generative AI Hub
Managed hosting and routing for built frontends
SAP's own guidance is narrower than the service's reach: it names standalone, single-tenant applications that do not connect to other applications as the fit, and says to stay on [the HTML5 Application Repository](artifact:btp-html5-application-repository) and the application router where those meet your needs better. Four hard limits decide it before taste does — 300 requests per second per subaccount, ten retained versions per application, 100 MB per application and 400 MB for the deployment archive.
Collects Cloud Foundry or Kyma logs into a searchable Kibana
Ingests and retains compliance audit data from BTP
OAuth server issuing JWTs and holding scopes for BTP apps
Cloud Foundry runtime of SAP BTP for polyglot applications
Development environment on BTP for UI5, Fiori, mobile and CAP
Proxy from cloud apps to on-premise systems via Cloud Connector
Predefined CI/CD pipelines for SAP development projects
Vault for an application's passwords, keys and keyrings
Named, credentialed addresses of other systems resolved at runtime
Extracts header fields and line items from business documents
APIs and a UI5 component for document management in apps
Boolean and string flags read by applications at runtime
Managed SAP HANA database service on BTP
Provisioned per plan and per component, so capacity and cost are decisions taken before any model exists. And it is the database, not a warehouse — modelling, loading and cataloguing are the products above it, and reaching it directly bypasses every semantic they add.
Stores UI5 and HTML5 apps and serves them through the approuter
Event streaming and management platform in Integration Suite
Calls an application endpoint on a schedule and logs each run
SAP's AI engagement layer across SAP applications
Scans uploaded files over REST with ClamAV
Registers a multitenant application for subaccount subscriptions
One inbox for tasks across SAP applications and BTP workflows