Neon

Neon's official MCP hooks Claude directly into your serverless Postgres infrastructure. You can spin up branches, run SQL queries, inspect schemas, and tweak database settings without leaving the chat window. It's the first MCP I've seen that treats database branching as a first-class citizen, which makes sense given Neon's architecture. The standout workflow is schema iteration. You describe a change, Claude generates the migration SQL, creates a branch, runs it, and you can test before merging. No context switching, no copy-pasting connection strings. I've used it to prototype table structures during design discussions, and it's faster than opening a separate SQL client. The ability to query across multiple projects is handy if you're juggling staging and production environments. Quirks: it assumes you're already a Neon user. There's no onboarding for new accounts, so you'll need API credentials and at least one project set up beforehand. The SQL execution is straightforward but doesn't handle complex transactions or long-running queries gracefully. If you're doing bulk data work, you'll still want a proper client. Also, while it can create branches, it won't auto-clean them up, so you'll accumulate test branches unless you're disciplined. The install is dead simple via npx, and it works across Claude Desktop, Cursor, and VS Code without fuss. The pre-listed use cases (spinning up branches, ad-hoc SQL, schema migrations) are accurate, not aspirational. I'd reach for this when prototyping or debugging schema issues in conversation with an AI. If you're not using Neon or don't work with branching workflows, it won't change your life. Skip it if you're on a traditional Postgres setup or prefer GUI tools for schema work. This is for developers who already like Neon's branching model and want to control it conversationally. It's competent, focused, and doesn't try to be more than it is.