Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. Use for any Neon-related questions.
Neon is a serverless Postgres platform that separates compute and storage to offer autoscaling, branching, instant restore, and scale-to-zero. It's fully compatible with Postgres and works with any language, framework, or ORM that supports Postgres.
Activate this skill when users want to:
@neondatabase/serverless driver or @neondatabase/neon-js SDKThe Neon MCP server is required for project and database management. It uses OAuth and authenticates via browser on first use — no API key needed.
If MCP tools are not available, guide the user through manual setup:
The Neon MCP server should be configured automatically via this plugin. If it isn't, the user can add it manually:
codex mcp add neon --url https://mcp.neon.tech/mcp
Restart Codex, then verify by attempting to list projects.
Direct the user to the Neon MCP docs for setup steps: https://neon.com/docs/ai/neon-mcp-server
The Neon documentation is the source of truth for all Neon-related information. Always verify claims against the official docs before responding. Neon features and APIs evolve, so prefer fetching current docs over relying on training data.
Any Neon doc page can be fetched as markdown in two ways:
.md to the URL (simplest): https://neon.com/docs/introduction/branching.mdtext/markdown on the standard URL: curl -H "Accept: text/markdown" https://neon.com/docs/introduction/branchingBoth return the same markdown content. Use whichever method your tools support.
The docs index lists every available page with its URL and a short description: