Neon MCP

Neon is serverless Postgres with database branching, where a branch is a copy on write clone of the data that spins up in seconds and can be discarded just as fast. Its MCP server exposes both that control plane and the SQL surface, which makes it one of the few database integrations where an agent can experiment without putting the main database at risk. An agent connected to it can list and create projects, create, list and delete branches, fetch connection strings, describe database and table schemas, and execute SQL against a chosen branch. It also supports a migration pattern that fits agents specifically: the change is applied to a temporary branch first, verified there, then committed to the main branch, so a migration that breaks something never lands on production data in the first place. This is built for developers working on a Neon project with an assistant in the editor. The assistant reads the real schema instead of guessing from model files, tries a query against a branch, and proposes a migration for approval before anything is committed. The usual caution for SQL access applies: the connection carries whatever permissions its role has, so use a limited role and keep destructive statements behind human review.