> Full Neon documentation index: https://neon.com/docs/llms.txt

# Electric joins Neon, a Vercel AI SDK provider for the AI Gateway, and agent skills everywhere

## Electric joins Neon

**Electric, the team behind the Electric sync engine and PGlite, is joining Neon.** The sync engine keeps data continuously synchronized between a central Postgres database and connected clients such as browser tabs, mobile apps, and agents, so you can build real-time, collaborative, and agentic apps without hand-rolling websockets, caching, and a sync layer.

Real-time sync is hard to get right on your own: conflict resolution, partial replication, and reconnection logic are difficult to build from scratch. Electric turns it into a reusable primitive that handles the hard parts, so agents can add live, collaborative features by default instead of wiring up sync themselves.

Electric is coming to the Neon platform alongside Neon's other backend services ([Lakebase Postgres](https://neon.com/docs/postgres/overview), [Auth](https://neon.com/docs/auth/overview), [Storage](https://neon.com/docs/storage/overview), [Functions](https://neon.com/docs/compute/functions/overview), and the [AI Gateway](https://neon.com/docs/ai-gateway/overview)), with deeper integration already underway. To get familiar now, our [guide to Electric on Neon](https://neon.com/guides/electric-sql) walks through real-time sync with Shapes and a React app.

Read the full announcement: [Electric is joining team Neon at Databricks](https://neon.com/blog/electric-joins-neon).

## Neon AI Gateway is now a Vercel AI SDK provider

The [Neon AI Gateway](https://neon.com/docs/ai-gateway/overview) gives you one API and one credential for 42+ frontier and open-source models (OpenAI, Anthropic, Google, and more), built into your Neon branch. It's now a [community provider for the Vercel AI SDK](https://ai-sdk.dev/providers/community-providers/neon-ai-gateway): point the SDK at your branch and swap models without per-provider SDKs or keys.

```ts
import { neon } from '@neon/ai-sdk-provider';
import { generateText } from 'ai';

const { text } = await generateText({
  model: neon('gpt-5-mini'),
  prompt: 'What is serverless Postgres?',
});
```

Set `NEON_AI_GATEWAY_BASE_URL` and `NEON_AI_GATEWAY_TOKEN` from your branch, or pull them with `neon env pull`.

**Info: Free AI Gateway credits on paid plans**

While in beta, Neon paid-plan users get free AI Gateway credits. To try it out, see [Get started with Neon AI Gateway](https://neon.com/docs/ai-gateway/get-started).

## Neon's skills and MCP install in any agent

### Support for Agent Plugins 1.0.0

Neon's [agent skills and MCP server](https://github.com/neondatabase/agent-skills) now ship as an [Agent Plugins](https://agent-plugins.org/) package, an open standard for extending agents with skills and MCP. Point any conforming client, such as Cursor, Codex, GitHub Copilot, Kiro, or VS Code, at the repo to load them straight from source.

All existing native plugins remain available:

- Claude Code: `/plugin marketplace add neondatabase/agent-skills`, then `/plugin install neon-postgres@neon`
- Cursor: `/add-plugin neon-postgres`
- Kimi Code: `/plugins install https://github.com/neondatabase/agent-skills`

## Neon CLI updates

The CLI keeps growing. Recent additions include a branch-first workflow (`neon link`, `neon checkout`, `neon psql`, `neon data-api`) and commands for the new backend services (`neon functions`, `neon buckets`); see the [CLI reference](https://neon.com/docs/cli) for the full set. Two of the latest:

`neon env pull` gained a `--service` flag to pull credentials for only the services you name, repeatable for more than one:

```bash
neon env pull --service ai-gateway --service postgres
```

`neon open` (neonctl 3.2.0) opens your linked project's dashboard in the Neon Console, straight from the terminal:

```bash
neon open
```

## Inspect a database from the Neon MCP server

We first shipped these diagnostics as the [`neon inspect db`](https://neon.com/docs/cli/inspect) CLI command. The same checks are now built into the [Neon MCP server](https://neon.com/docs/ai/neon-mcp-server) as the `inspect_database` tool. It runs the same 14 read-only diagnostics: table and index sizes, unused indexes, sequential scans, long-running queries and locks, heavy and frequent statements, cache hit rate and working set, autovacuum and bloat, and replication state. Ask your assistant why a branch is slow or large without writing catalog SQL by hand.

Don't have the MCP server set up yet? Install it with `neon init`:

```bash
npx neon@latest init
```

## Neon for Herdr

Neon for Herdr puts a live Neon pane in your Herdr terminal workspace. Browse projects, create and reset branches, start or suspend compute, and copy connection strings without leaving your editor.

```bash
herdr plugin install neon-solutions/neon-herdr
herdr plugin action invoke neon.herdr.dashboard
```

Read the post: [Neon for Herdr: a Neon pane in your Herdr workspace](https://neon.com/blog/neon-for-herdr-a-neon-pane-in-your-herdr-workspace).

<details>

<summary>**New NAT gateway IPs and VPC endpoint services in US West (Oregon) and Asia Pacific (Singapore)**</summary>

We've added NAT gateway IP addresses and VPC endpoint service addresses for Private Networking in AWS US West (Oregon) (`us-west-2`) and Asia Pacific (Singapore) (`ap-southeast-1`).

**Tip: Update your IP allowlists**

If you allowlist Neon's NAT gateway IPs on external systems, add the new addresses, or connections may be affected intermittently.

See [Regions](https://neon.com/docs/introduction/regions#aws-nat-gateway-ip-addresses) for the full IP list and the [Private Networking guide](https://neon.com/docs/guides/neon-private-networking) for VPC endpoint services by region.

</details>
