Integrate with Neon Serverless Postgres

Using Neon is a skill for working with Neon, a serverless Postgres platform that separates compute and storage to offer autoscaling, branching, instant restore, and scale-to-zero, while staying fully Postgres-compatible with any language, framework, or ORM that supports Postgres. Rather than answering Neon questions from memory, it always references the live Neon documentation as the source of truth, fetching the index of all docs via curl https://neon.com/llms.txt and any specific page as markdown via a similar authenticated-header request, and explicitly avoids guessing at documentation URLs.

It organizes that documentation into four resource groups, each mapped to a references/*.md file. Core Guides cover what Neon is and its architecture, how to reference and verify official docs, its features (branching, autoscaling, scale-to-zero, instant restore), getting started (project setup, connection strings, dependencies, schema), choosing a connection method by platform and runtime, and developer tools (the VS Code extension, an MCP server, and the Neon CLI's neon init). Database Drivers and ORMs cover the @neondatabase/serverless driver for HTTP/WebSocket queries from serverless or edge functions, and Drizzle ORM integration. Auth and Data API SDKs cover @neondatabase/auth for authentication only, and the @neondatabase/neon-js SDK for authentication plus a PostgREST-style data API. Platform API and CLI cover managing Neon resources programmatically through the REST Platform API, the Neon CLI for terminal workflows and CI/CD pipelines, a TypeScript SDK (@neondatabase/api-client), and a Python SDK (the neon-api package).

curl https://neon.com/llms.txt

Use it when working with Neon Serverless Postgres - setting up a Neon database, choosing a connection method, using features like branching or autoscaling, working with Neon authentication or APIs, or asking about Neon best practices. It is scoped specifically to Neon; for a different Postgres provider or a non-Neon-specific database question, it does not apply, since its whole value is routing to the correct Neon-specific documentation page rather than general Postgres knowledge.

Input is the Neon-related task or question, including which area it touches (setup, connections, drivers, auth, platform API, or CLI). Output is the answer grounded in the correct fetched Neon documentation page for that area, pointed to the matching references/*.md resource rather than answered from unverified memory.

Developers setting up or integrating with Neon serverless Postgres who want documentation-grounded guidance across drivers, ORMs, authentication, the Data API, and the Platform API/CLI, rather than an answer that risks being stale or unverified - including teams migrating an existing Postgres workload onto Neon's branching and scale-to-zero model, and teams automating Neon project or branch management from a script or CI/CD pipeline via its CLI or SDKs.