prisma · gregory-boch-prisma · Aug 20, 2026 · Aug 20, 2026
diff --git a/.claude-plugin/marketplace.json b/.claude-plugin/marketplace.json
@@ -1,17 +1,18 @@
 {
   "name": "prisma",
-  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, and database workflows, plus official Prisma MCP integration.",
+  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, MongoDB upgrade paths, and database workflows, plus official Prisma MCP integration.",
   "owner": {
     "name": "Prisma"
   },
   "plugins": [
     {
       "name": "prisma",
       "source": "./",
-      "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, and database workflows, plus official Prisma MCP integration.",
-      "version": "0.3.0",
+      "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, MongoDB upgrade paths, and database workflows, plus official Prisma MCP integration.",
+      "version": "0.4.0",
       "author": {
         "name": "Prisma",
+        "email": "support@prisma.io",
         "url": "https://www.prisma.io/"
       },
       "repository": "https://github.com/prisma/prisma-plugin",
@@ -21,6 +22,7 @@
         "orm",
         "database",
         "postgresql",
+        "mongodb",
         "migrations",
         "prisma-client",
         "prisma-postgres",

diff --git a/.claude-plugin/plugin.json b/.claude-plugin/plugin.json
@@ -1,9 +1,10 @@
 {
   "name": "prisma",
-  "version": "0.3.0",
-  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, and database workflows, plus official Prisma MCP integration.",
+  "version": "0.4.0",
+  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, MongoDB upgrade paths, and database workflows, plus official Prisma MCP integration.",
   "author": {
     "name": "Prisma",
+    "email": "support@prisma.io",
     "url": "https://www.prisma.io/"
   },
   "homepage": "https://www.prisma.io/docs",
@@ -14,6 +15,7 @@
     "orm",
     "database",
     "postgresql",
+    "mongodb",
     "migrations",
     "prisma-client",
     "prisma-postgres",

diff --git a/.codex-plugin/plugin.json b/.codex-plugin/plugin.json
@@ -1,9 +1,10 @@
 {
   "name": "prisma",
-  "version": "0.3.0",
-  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, and database workflows, plus official Prisma MCP integration.",
+  "version": "0.4.0",
+  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, MongoDB upgrade paths, and database workflows, plus official Prisma MCP integration.",
   "author": {
     "name": "Prisma",
+    "email": "support@prisma.io",
     "url": "https://www.prisma.io/"
   },
   "homepage": "https://www.prisma.io/docs",
@@ -14,6 +15,7 @@
     "orm",
     "database",
     "postgresql",
+    "mongodb",
     "migrations",
     "prisma-client",
     "prisma-postgres",
@@ -28,7 +30,7 @@
   "interface": {
     "displayName": "Prisma",
     "shortDescription": "Curated Prisma skills with official MCP integration",
-    "longDescription": "Bring Prisma expertise into Codex with curated skills for Prisma CLI, Prisma Client, database setup, Prisma Postgres provisioning and operations, Prisma Compute app deployment, Prisma ORM v7 upgrades, and Prisma driver adapter implementation, plus official Prisma MCP server configuration for schema-aware and account-aware database workflows.",
+    "longDescription": "Bring Prisma expertise into Codex with curated skills for Prisma CLI, Prisma Client, database setup, Prisma Postgres provisioning and operations, Prisma Compute app deployment, Prisma ORM v7 upgrades, MongoDB v6 upgrade decisions, and Prisma driver adapter implementation, plus official Prisma MCP server configuration for schema-aware and account-aware database workflows.",
     "developerName": "Prisma",
     "category": "Coding",
     "capabilities": [

diff --git a/.cursor-plugin/plugin.json b/.cursor-plugin/plugin.json
@@ -1,7 +1,7 @@
 {
   "name": "prisma",
-  "version": "0.3.0",
-  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, and database workflows, plus official Prisma MCP integration.",
+  "version": "0.4.0",
+  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, MongoDB upgrade paths, and database workflows, plus official Prisma MCP integration.",
   "author": {
     "name": "Prisma",
     "email": "support@prisma.io",
@@ -17,6 +17,7 @@
     "schema",
     "migration",
     "postgresql",
+    "mongodb",
     "mysql",
     "sqlite",
     "prisma-postgres",

diff --git a/.plugin/plugin.json b/.plugin/plugin.json
@@ -1,9 +1,10 @@
 {
   "name": "prisma",
-  "version": "0.3.0",
-  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, and database workflows, plus official Prisma MCP integration.",
+  "version": "0.4.0",
+  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, MongoDB upgrade paths, and database workflows, plus official Prisma MCP integration.",
   "author": {
     "name": "Prisma",
+    "email": "support@prisma.io",
     "url": "https://www.prisma.io/"
   },
   "homepage": "https://www.prisma.io/docs",
@@ -14,6 +15,7 @@
     "orm",
     "database",
     "postgresql",
+    "mongodb",
     "migrations",
     "prisma-client",
     "prisma-postgres",

diff --git a/LICENSE b/LICENSE
@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Prisma
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/README.md b/README.md
@@ -8,14 +8,27 @@ Prisma plugin for agent tools, including curated skills for Prisma ORM, Prisma C
 npx plugins add prisma/prisma-plugin
 ```
 
+## Agent Plugins Standard
+
+This repository conforms to the [Agent Plugins](https://agent-plugins.org) open standard (v1.0.0):
+
+- `plugin.json` — the portable manifest at the repository root
+- `mcp.json` — the portable MCP server declaration (official Prisma MCP over streamable HTTP)
+- `skills/` — one directory per skill with an Agent Skills `SKILL.md`
+
+Any Agent Plugins–compatible client (ChatGPT/Codex, Cursor, GitHub Copilot, VS Code, Kiro, and others) can consume these files directly. The client-specific directories (`.claude-plugin/`, `.codex-plugin/`, `.cursor-plugin/`, `.plugin/`) are kept for clients and installers that predate the standard; the portable files at the root are the source of truth.
+
 ## Supported Tools
 
 | Tool | Support |
 | --- | --- |
+| Agent Plugins clients (VS Code, Copilot, Kiro, …) | Skills and Prisma MCP via the portable standard files |
 | OpenAI Codex | Skills and Prisma MCP |
 | Claude Code | Skills and Prisma MCP |
 | Cursor | Rules, skills, and Prisma MCP metadata |
 
+Codex also discovers this repository directly as a plugin marketplace via `.agents/plugins/marketplace.json`; the repo-root plugin path (`"./"`) requires Codex 0.142.0 or newer.
+
 ## What's Included
 
 - Prisma CLI guidance for setup, migrations, database commands, Studio, and MCP
@@ -26,6 +39,7 @@ npx plugins add prisma/prisma-plugin
 - Prisma Compute guidance for app deployment, `prisma.compute.ts`, `@prisma/cli app deploy`, `create-prisma --deploy`, framework readiness, logs, env vars, domains, and monorepos
 - Prisma driver adapter implementation guidance for Prisma ORM v7 adapter contracts
 - Prisma ORM 7 upgrade guidance
+- Prisma MongoDB upgrade decision guidance for v6 projects (stay on v6 vs Prisma Next)
 - Cursor rules for Prisma schema and migration best practices
 
 ## Skills
@@ -35,6 +49,7 @@ npx plugins add prisma/prisma-plugin
 - `prisma-compute`
 - `prisma-database-setup`
 - `prisma-driver-adapter-implementation`
+- `prisma-mongodb-upgrade`
 - `prisma-postgres`
 - `prisma-postgres-setup`
 - `prisma-upgrade-v7`
diff --git a/mcp.json b/mcp.json
@@ -0,0 +1,9 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/mcp.schema.json",
+  "mcpServers": {
+    "prisma": {
+      "type": "streamable-http",
+      "url": "https://mcp.prisma.io/mcp"
+    }
+  }
+}
diff --git a/plugin.json b/plugin.json
@@ -0,0 +1,29 @@
+{
+  "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
+  "name": "prisma",
+  "version": "0.4.0",
+  "description": "Curated Prisma skills for ORM, Prisma Client, Prisma Postgres, Prisma Compute deployments, driver adapters, migrations, upgrades, MongoDB upgrade paths, and database workflows, plus official Prisma MCP integration.",
+  "author": {
+    "name": "Prisma",
+    "email": "support@prisma.io",
+    "url": "https://www.prisma.io/"
+  },
+  "homepage": "https://www.prisma.io/docs",
+  "repository": "https://github.com/prisma/prisma-plugin",
+  "license": "MIT",
+  "keywords": [
+    "prisma",
+    "orm",
+    "database",
+    "postgresql",
+    "mongodb",
+    "migrations",
+    "prisma-client",
+    "prisma-postgres",
+    "prisma-compute",
+    "driver-adapters",
+    "upgrades",
+    "deployment",
+    "mcp"
+  ]
+}
diff --git a/skills/prisma-database-setup/SKILL.md b/skills/prisma-database-setup/SKILL.md
@@ -170,7 +170,7 @@ generator client {
 }
 ```
 
-For MongoDB, stay on the latest Prisma 6.x line and keep the connection URL in `schema.prisma`. Do not move a MongoDB project to the Prisma 7 SQL adapter setup.
+For MongoDB, stay on the latest Prisma 6.x line and keep the connection URL in `schema.prisma`. Do not move a MongoDB project to the Prisma 7 SQL adapter setup. If a MongoDB project asks about upgrading Prisma versions, route to the `prisma-mongodb-upgrade` skill (stay-on-v6 vs Prisma Next is the real decision; Prisma 7 is not an option).
 
 ## Rule Files
 

diff --git a/skills/prisma-mongodb-upgrade/SKILL.md b/skills/prisma-mongodb-upgrade/SKILL.md
@@ -0,0 +1,92 @@
+---
+name: prisma-mongodb-upgrade
+description: Decision and migration guide for Prisma ORM MongoDB projects on v6, which have no upgrade path to v7. Use when a MongoDB project asks about upgrading Prisma, when "upgrade to prisma 7" comes up in a project with provider = "mongodb", or when evaluating a move to Prisma Next. Triggers on "upgrade prisma mongodb", "prisma 7 mongodb", "mongodb prisma migration", "prisma next mongodb".
+license: MIT
+metadata:
+  author: prisma
+  version: "0.1.0"
+---
+
+# Prisma MongoDB Upgrade Path
+
+MongoDB projects are the one Prisma cohort with no road into Prisma 7: **v6 is the terminal
+classic-ORM major for MongoDB, and v7 never ships a MongoDB connector**. The successor path
+is [Prisma Next](https://github.com/prisma/prisma-next), where MongoDB support is in Early
+Access with GA planned after Postgres. This skill frames the real decision — migrate to
+Prisma Next (the encouraged path), or stay on v6 where a hard blocker applies — and carries
+the migration mechanics.
+
+**Never do either of these:**
+
+- Never advise a MongoDB project to "upgrade to Prisma 7". The connector does not exist
+  there. The `prisma-upgrade-v7` guide does not apply to MongoDB projects.
+- Never solve the version question by rewriting the app onto a SQL database. Changing the
+  database engine is a separate, much larger decision that is not yours to make implicitly.
+
+## The version landscape
+
+| Version | MongoDB status |
+|---------|----------------|
+| Prisma ORM v6 | Fully supported (`mongodb` provider); latest 6.x is the current stable path; maintenance line |
+| Prisma ORM v7 | **No MongoDB connector — not an option, ever** |
+| Prisma Next | MongoDB support in **Early Access**, actively developed, GA planned after Postgres — the successor path for MongoDB projects |
+
+## The decision, up front
+
+**Migrating to Prisma Next is the encouraged path.** MongoDB support in Prisma Next is Early
+Access: functional and moving quickly, with GA planned after Postgres — and the Prisma team
+wants MongoDB users to migrate early and share feedback. The migration mechanics are
+detailed in the references.
+
+**Staying on the latest v6 remains a legitimate choice where a hard blocker applies** —
+stated plainly: the Next Mongo façade does not wrap transactions yet (the underlying driver
+is available directly; this is expected to change soon), and pre-1.0 minors can carry
+breaking changes with published upgrade recipes.
+
+### Decision table
+
+| Signal | Direction |
+|--------|-----------|
+| No blockers below apply | Migrate to Next; run the `verify-cutover-checklist` and share feedback with the Prisma team |
+| Greenfield / prototype / internal tool | Migrate to Next |
+| Codebase uses multi-document transactions (`$transaction`) — check with grep, do not ask | Plan raw-driver session equivalents first (see `client-api-mapping`), or stay on v6 until the façade wrapper lands |
+| Team cannot absorb pre-1.0 breaking upgrades between minors | Stay on v6 until GA |
+| Risk-averse but interested | Run a staged Next round-trip on a copy (see `verify-cutover-checklist`), then migrate |
+
+Note: the transactions gap is expected to close soon — this section will be updated when
+façade transactions merge in Prisma Next.
+
+### If staying on v6: hygiene (a deliberate stay, not neglect)
+
+- Pin the Prisma packages to the latest 6.x line and keep taking 6.x patch releases.
+- Track Prisma release notes and security advisories for the 6.x line.
+- Keep the classic v6 MongoDB setup: `url = env("DATABASE_URL")` in the schema, `db push`
+  workflow, no SQL driver adapters (see `prisma-database-setup` for the v6 MongoDB shape).
+- Re-evaluate when Prisma Next's MongoDB is GA, or when blockers for trying EA are resolved.
+
+## Reference files
+
+| Reference | What it covers |
+|-----------|----------------|
+| `references/decision-stay-or-migrate.md` | The full decision framing, blocker checks, and stay-hygiene detail |
+| `references/schema-contract-mapping.md` | v6 schema (`mongodb` provider, `@db.ObjectId`, composite types) → Next contract concepts |
+| `references/client-api-mapping.md` | v6 client calls → Next equivalents, incl. raw escape hatches and transactions — names map, parity does not |
+| `references/migrations-mapping.md` | v6 `db push`-only story → Next's plan/migrate/verify/sign flow |
+| `references/verify-cutover-checklist.md` | No-data-moves verification: same DB, index parity, staged round-trip before cutover |
+
+## Verified against
+
+Behavioral claims about Prisma Next in this skill were verified against
+[prisma/prisma-next](https://github.com/prisma/prisma-next) at commit
+`a2791c5dd59d579b4b3052942ae7f8fe5e2ee852` (pre-1.0, ~v0.14/0.15 line). Prisma Next moves
+quickly in Early Access: **before acting on any Next-side claim, verify it against the
+version actually installed** (check the project's `@prisma-next/*` versions and the
+prisma-next skills installed with it). Next's Mongo target requires MongoDB 8.0+ and expects
+`mongodb@^7` as a user-supplied peer dependency.
+
+## Hand-off rule
+
+This skill is the **discovery bridge**, not a replacement for Prisma Next's own
+documentation. After a project switches to Prisma Next, run Prisma Next's `init`/skill
+installation and follow its own skills (quickstart, contract, queries, migrations, runtime)
+for day-to-day work — do not keep working from this skill's summaries.
diff --git a/skills/prisma-mongodb-upgrade/references/client-api-mapping.md b/skills/prisma-mongodb-upgrade/references/client-api-mapping.md
@@ -0,0 +1,61 @@
+# client-api-mapping
+
+How v6 Prisma Client calls map to Prisma Next's Mongo client — names map, parity does not.
+
+## Priority
+
+CRITICAL
+
+## Why It Matters
+
+The v6 and Next client APIs look superficially similar, but none of the v6 MongoDB raw
+methods exist under their old names, aggregation moved to a different lane entirely, and
+transactions go through the driver rather than a façade wrapper. Assuming parity produces
+code that does not compile — or, in the transactions case, code that silently loses
+atomicity.
+
+## The mapping
+
+| v6 call | Prisma Next equivalent | Notes |
+|---------|------------------------|-------|
+| `prisma.user.findMany(...)` | `db.orm.users.where(...).all()` | Fluent ORM lane; storage-name keys (see `schema-contract-mapping.md`) |
+| `prisma.user.findFirst(...)` | `db.orm.users.where(...).first()` | |
+| `create` / `update` / `upsert` / `delete` / `updateMany` / `deleteMany` | `create` / `update` / `upsert` / `delete` / `updateAll` / `deleteAll` on `db.orm.<collection>` | See Prisma Next's `prisma-next-queries` skill |
+| `prisma.user.aggregate(...)`, `groupBy(...)` | **No ORM equivalent.** Use the typed aggregation-pipeline builder: `db.query.from(...).match(...).group(...).build()` | Prisma Next's `prisma-next-queries` skill covers the builder lane |
+| `$runCommandRaw(...)` ([v6 docs](https://www.prisma.io/docs/orm/prisma-client/using-raw-sql/raw-queries#runcommandraw)) | **Name does not exist in Next.** Raw lane is `mongoRaw(...)` → a raw collection with `aggregate`, `insertOne/Many`, `updateOne/Many`, `deleteOne/Many`, `findOneAndUpdate/Delete`. For arbitrary database commands, use the underlying `mongodb` driver directly — it is a user-supplied peer dependency and fully accessible | Check the installed version's raw surface |
+| `<model>.findRaw(...)` ([v6 docs](https://www.prisma.io/docs/orm/prisma-client/using-raw-sql/raw-queries#findraw)) | `mongoRaw(...)` collection reads (e.g. `aggregate` with a `$match` stage) | No direct `findRaw` name |
+| `<model>.aggregateRaw(...)` ([v6 docs](https://www.prisma.io/docs/orm/prisma-client/using-raw-sql/raw-queries#aggregateraw)) | `mongoRaw(...).aggregate(...)` or the typed pipeline builder | |
+| `$transaction(...)` — works on v6 with a replica set ([v6 docs](https://www.prisma.io/docs/orm/overview/databases/mongodb#replica-set-configuration)) | The façade does not wrap `db.transaction(...)` yet, **but the underlying `mongodb` driver is directly available** (user-supplied peer dependency): multi-document atomicity works today via driver sessions (`client.startSession()` / `session.withTransaction(...)`) on a replica set | A façade wrapper is expected soon; this row will be updated when it merges |
+| `$connect` / `$disconnect` | `connect()` / `close()` on the Mongo façade client | |
+
+## Bad
+
+```typescript
+// Assuming v6 names exist in Prisma Next:
+await db.user.$runCommandRaw({ collStats: 'users' }); // no such method
+await db.transaction(async (tx) => { ... });          // no such method on the Mongo façade
+```
+
+## Good
+
+```typescript
+// Raw lane under its Next name:
+const raw = mongoRaw(db);
+await raw.users.aggregate([{ $match: { status: 'active' } }]);
+
+// Aggregation through the typed pipeline builder:
+const stats = await db.query.from('users').group({ _id: '$role', n: { $count: {} } }).build();
+
+// Multi-document atomicity today: the mongodb driver (a direct dependency of the
+// project) exposes sessions and transactions as usual:
+const session = mongoClient.startSession();
+await session.withTransaction(async () => {
+  // ...writes...
+});
+```
+
+## References
+
+- [v6 MongoDB raw queries](https://www.prisma.io/docs/orm/prisma-client/using-raw-sql/raw-queries#raw-queries-with-mongodb)
+- [v6 replica set requirement for transactions](https://www.prisma.io/docs/orm/overview/databases/mongodb#replica-set-configuration)
+- Prisma Next queries + runtime skills (`skills/prisma-next-queries`, incl. its dedicated `mongo.md`; `skills/prisma-next-runtime`) — authoritative for the Next side; verified @ `a2791c5dd59d579b4b3052942ae7f8fe5e2ee852`
-Original file line number
+Diff line change
@@ Expand Up / @@ -170,7 +170,7 @@ generator client { @@
     }
     ```
-    For MongoDB, stay on the latest Prisma 6.x line and keep the connection URL in `schema.prisma`. Do not move a MongoDB project to the Prisma 7 SQL adapter setup.
+    For MongoDB, stay on the latest Prisma 6.x line and keep the connection URL in `schema.prisma`. Do not move a MongoDB project to the Prisma 7 SQL adapter setup. If a MongoDB project asks about upgrading Prisma versions, route to the `prisma-mongodb-upgrade` skill (stay-on-v6 vs Prisma Next is the real decision; Prisma 7 is not an option).
     ## Rule Files
@@ Expand Down @@