CDS pluginCDS plugintypeInstalls into a CAP project and extends the runtime. CAP loads it through cds.requires or the plugin hook.See every one →What this type is →independently maintainedindependently maintainedoriginPublished by one person or a small company outside SAP. Says nothing about quality; the readings say that.See every one →

cds-mongodb

MongoDB as a native CAP database service, through Mongoose — CQN reads and writes, managed associations as ObjectId references, $expand resolved by populate, and cds deploy --to mongoose.

CAP's database services are relational; this answers the document-oriented case without changing how the model or the services are written. Associations become ObjectId references and expand maps onto Mongoose populate, which is where the impedance actually shows.

Facts

Latestv1.0.1ReleasedLicenceApache License Version 2.0

Where it sits

Lives in
Provides
Database connectorsCAPDatabase connectorscapabilityConnecting an application’s data model and queries to a database, including the differences in supported queries, types and schema management between database implementations. Changing an existing schema belongs to [schema evolution](capability:schema-evolution).
Flavors
Node.jsfrom its runtime
Requires
MongoDBMongoDBoutside the atlasThe database itself, reached through Mongoose. The plugin is the adapter, not the store.

Who is behind it

abdulmuqeetosama99

Before choosing this

Conditions

LicenceSAP Developer License Agreement 3.2 CAP§ 1, 2, 3A cds-plugin is used with SAP CAP materials, or an artifact is explicitly identified as a CAP plugin or application.
  • § 1 License. Productive customer applications are limited to SAP BTP or another SAP-licensed platform, and mass extraction to a non-SAP product is restricted except where solely required for SAP interoperability.
  • § 2 Intellectual Property. The agreement retains SAP's rights in the covered materials and limits making APIs, tools or software available to third parties, while preserving ownership of customer applications subject to SAP's underlying rights.
  • § 3 Artificial Intelligence Training. The agreement prohibits use of the covered materials and customer applications for training artificial-intelligence models or systems.
SAP Developer License Agreement 3.2 CAP →

Also, from Database connectors§ 1: The connector itself does not decide the licence boundary. Section 1 makes the destination and purpose of extraction relevant, including the scoped exception for interoperability with an SAP product.

PracticalFunctional boundary

It declares no peer range on @sap/cds and publishes no repository, so there is nothing to read but the package itself and no CI to look at.

What it declares

Every artifact

Type
CDS plugin
Origin
Independently maintained
Runtime
Node.js

As a CDS plugin

Distributed through
npm

Connections2

Install

npm add cds-mongodb

Derived from the package name. No recipe recorded; the README has the configuration.

Where it sits in your app

Download
Your CAP applicationdocumentedrequiresMongoDB, systemMongoDBsystemcds-mongodb, modulecds-mongodb
SAPnot SAP's, or the project's owndocumented only

README

quoted from cds-mongodb@1.0.1, read
cds-mongodb@1.0.1/README.mdOn npm

cds-mongodb

MongoDB (Mongoose) persistence adapter for SAP Cloud Application Programming Model (CAP).

cds-mongodb enables CAP applications to use MongoDB as a native persistence layer, providing a developer experience consistent with official CAP database services such as @cap-js/sqlite and @cap-js/hana.


excerpt, Apache License Version 2.0, read licencethe rest, on npm

History

Latest

v1.0.1

  1. v1.0.0

On npm
4downloads per week, npm
Weekly downloads for cds-mongodb26 complete calendar weeks from 2026-04-20 to 2026-10-18; the latest total is 4.20 Apr – 26 Apr: 427 Apr – 3 May: 44 May – 10 May: 1011 May – 17 May: 418 May – 24 May: 625 May – 31 May: 61 Jun – 7 Jun: 48 Jun – 14 Jun: 615 Jun – 21 Jun: 222 Jun – 28 Jun: 529 Jun – 5 Jul: 76 Jul – 12 Jul: 413 Jul – 19 Jul: 220 Jul – 26 Jul: 327 Jul – 2 Aug: 13 Aug – 9 Aug: 310 Aug – 16 Aug: 417 Aug – 23 Aug: 324 Aug – 30 Aug: 731 Aug – 6 Sept: 87 Sept – 13 Sept: 314 Sept – 20 Sept: 621 Sept – 27 Sept: 928 Sept – 4 Oct: 15 Oct – 11 Oct: 312 Oct – 18 Oct: 4
Database connectors
  1. SAP HANA CloudManaged SAP HANA database service on BTP
  2. PostgreSQL on SAP BTP, hyperscaler optionManaged PostgreSQL from the hyperscaler via a BTP service binding
  3. com.sap.cds:cds-feature-hanaSAP HANA Cloud datasource for CAP Java applications
  4. com.sap.cds:cds-feature-jdbcJDBC runtime for H2 and SQLite in CAP Java
  5. com.sap.cds:cds-feature-postgresqlPostgreSQL datasource for CAP Java applications
  6. com.sap.cds:cds-services-bomMaven bill of materials pinning CAP Java module versions
  7. @cap-js/db-serviceBase service shared by CAP's SQLite, PostgreSQL and HANA services
  8. @cap-js/hanaSAP HANA database service for CAP
  9. @cap-js/postgresPostgreSQL database service for CAP
  10. @cap-js/sqliteSQLite database service for CAP, in memory during development
  11. cap-postgres-btp-connectivityTunnels CAP Node.js to a private PostgreSQL via Cloud Connector
  12. @cds-pgroll/postgresCLI for DROP and RENAME schema changes beside @cap-js/postgres
  13. @neoimpulse/cap-js-restore-model-defined-typesCAP plugin casting read values back to CDS model types
  14. @quadrio/cds-db2DB2 adapter for CDS
  15. @sap/cds-hanaDatabase adapter for SAP HANA in CAP
  16. @sap/cdsCAP Node.js runtime
  17. @sap/hana-clientSAP's Node.js driver for SAP HANA
  18. SAP HANASAP's relational database platform, on-premise and in HANA Cloud
  19. cds-pgPostgreSQL adapter for SAP CDS from the SAP Mentors community
  20. cap-snowflakeCAP database adapter for Snowflake with OData V4 support
  21. cds-mysqlMySQL and MariaDB database adapter for CAP

Details

Sources3
npm registrydiscovered here, keywords:sap-capchecked
npm registry, cds-mongodbversion, releases, installschecked
README.mdquoted, and what the entry declareschecked

Sources are graph entities: the same page may back several entries, and an unreachable source flags every row that rests on it.

Compatibility and provenance
runtimesnode
latestv1.0.1
first release
releases and cadence2
discovered vianpm registry · keywords:sap-cap
first seen in the atlas
ecosystem and domaincap, data-and-persistence
History in the atlas1
  1. First seen.
For your agent