---
collection: serverless-postgres
collection_name: Serverless Postgres
week_start: 2026-10-05
title: AI agents get deeper into the database as Postgres platforms open up their tooling
release_count: 47
generated: 2026-10-12
canonical: https://releases.sh/collections/serverless-postgres/digest/2026-10-05
---

# AI agents get deeper into the database as Postgres platforms open up their tooling

PlanetScale's MCP server learned to read branch metrics and org admins gained a cap on what AI clients can query, Neon opened every AI Gateway model to prepaid credits, and Prisma's v8 release candidate made migrations stop dropping data silently.

### Agents move closer to the metal

PlanetScale spent the week widening what an AI assistant can see and do against a database. The [MCP server can now pull branch metrics](https://planetscale.com/changelog/mcp-branch-metrics) — CPU, memory, disk, replication lag, and connections for Vitess, Postgres, and Neki branches — so an agent debugging a slow query can check the last hour of utilization without leaving the editor. With that much reach, the [organization-level cap on MCP query access](https://planetscale.com/changelog/mcp-query-access) arrives at the right moment: admins can set clients to no access, read-only, or read and write, applying to newly authorized clients while existing ones keep their grants.

Neon took the opposite tack on access, [opening every model in its AI Gateway catalog](https://neon.com/docs/changelog/2026-10-09) to paid plans with prepaid credits — no access request required, Claude Opus 5.5 included. Neon also added a way to complain about it: a `send_feedback` MCP tool and a `neon feedback` CLI command, plus `-y` flags on `neon deploy` and `neon config apply` for unattended runs.

### PlanetScale makes Postgres and migrations more elastic

PlanetScale Postgres gained [independently configurable dedicated read replicas](https://planetscale.com/changelog/postgres-dedicated-read-replicas), creatable in the primary region or a second region from the same cloud provider with their own cluster size, replica count, storage, and Postgres parameters — manageable from the dashboard, API, CLI, or Terraform.

Vitess users got a smaller but sharper fix: [deploy requests can retry only the failed tables](https://planetscale.com/changelog/retry-partially-failed-deploy-request) of a partially failed migration instead of restarting the whole deploy, leaving completed tables at their existing progress. The [PlanetScale CLI](https://github.com/planetscale/cli/releases/tag/v0.344.0) folded that in alongside Postgres extension toggles, VTGate parameter commands, human-readable sizes for keyspace `--max-storage` and `--storage`, and clearer messaging for expired or denied device logins.

### Prisma's v8 candidate stops dropping data quietly

Three release candidates landed for Prisma 8, and the headline change is about safety: [`prisma migration plan` and `prisma db update` now ask about every model or field a plan would drop](https://github.com/prisma/orm/releases/tag/v8.0.0-rc.17), answered with `--delete` or the new `--rename`, which keeps the rows. The ORM client picked up row locks, and `apply` and `scope` became `with` and `fragment`. Earlier in the week, [Prisma fixed a Bun install that could resolve two ArkType copies](https://github.com/prisma/orm/releases/tag/v8.0.0-rc.16) and break `prisma orm init` on a valid contract, and moved SQL contracts to explicit column data types like `pg/text`, with codecs validating every stored value and custom collection classes keeping their methods through the chain.

### Tracing, scopes, and smaller cleanups

Supabase's CLI shipped a large batch of beta and next-channel iterations plus a stable [v2.120.0 with opt-in OTLP tracing and persisted stack log history](https://github.com/supabase/cli/releases/tag/v2.120.0), the latter browsable via `stack logs history` and shipped to Analytics. The Client SDK [patched a remote code execution vulnerability in its realtime-js example](https://github.com/supabase/supabase-js/releases/tag/v2.117.3), corrected multipart field ordering for Storage uploads, and taught PostgREST to treat a TimeoutError as an abort in its retry guard; a canary also [stopped postgrest-typegen from emitting computed fields in `select('*')`](https://github.com/supabase/supabase-js/releases/tag/v2.118.0-canary.0).

Elsewhere, [Turso's CLI added scopes to org-wide API tokens](https://github.com/tursodatabase/turso-cli/releases/tag/v1.0.34), and the [Turso database pre-release](https://github.com/tursodatabase/turso/releases/tag/v0.8.3-pre.1) continued its 0.8.3 line. Prisma's language tools cycled through a run of insider and stable builds, and roughly a half-dozen lower-priority releases rounded out the week without changing the story.

## Releases covered

### Neon

- [Neon opens all AI Gateway models to prepaid credits, adds CLI and MCP feedback](https://neon.com/docs/changelog/2026-10-09)

### PlanetScale

- [PlanetScale MCP server adds planetscale_get_branch_metrics tool](https://planetscale.com/changelog/mcp-branch-metrics)
- [PlanetScale lets org admins cap MCP client query access](https://planetscale.com/changelog/mcp-query-access)
- [PlanetScale Postgres adds dedicated read replicas configurable per region](https://planetscale.com/changelog/postgres-dedicated-read-replicas)
- [PlanetScale deploy requests can retry only failed tables](https://planetscale.com/changelog/retry-partially-failed-deploy-request)
- [PlanetScale CLI v0.344.0 adds Postgres extension toggles and VTGate parameter commands](https://github.com/planetscale/cli/releases/tag/v0.344.0)

### Prisma

- [v8.0.0-rc.17](https://github.com/prisma/orm/releases/tag/v8.0.0-rc.17)
- [v8.0.0-rc.16](https://github.com/prisma/orm/releases/tag/v8.0.0-rc.16)

### Supabase

- [Supabase CLI v2.120.0 adds opt-in OTLP tracing and stack log history](https://github.com/supabase/cli/releases/tag/v2.120.0)
- [Supabase Client SDK v2.117.3 patches RCE in realtime-js example dependency](https://github.com/supabase/supabase-js/releases/tag/v2.117.3)
- [Supabase Client SDK v2.118.0-canary.0 changes computed field handling in postgrest-typegen](https://github.com/supabase/supabase-js/releases/tag/v2.118.0-canary.0)

### Turso

- [v1.0.34](https://github.com/tursodatabase/turso-cli/releases/tag/v1.0.34)
- [v0.8.3-pre.1](https://github.com/tursodatabase/turso/releases/tag/v0.8.3-pre.1)
