neondatabase / mcp-server-neon

The MCP server itself, hosted at mcp.neon.tech, exposes tools for listing and describing projects and branches, running SQL and SQL transactions, inspecting and comparing schemas, reviewing slow queries, explaining a query plan, and fetching a connection string — plus write-side tools, gated behind a separate OAuth or API-key scope, for creating and deleting projects and branches, running database migrations, and query tuning. Riding alongside that server are two skills with little connection to it: claimable-postgres, which documents Neon's separate "Claimable Postgres" product (neon.new) for spinning up a disposable, no-signup Postgres database over REST, CLI, or SDK; and logging-best-practices, a general canonical-log-line and wide-events guide that is not specific to Neon at all.

The MCP server is for a developer who wants an agent to administer their own Neon account by request rather than through the console or psql. The claimable-postgres skill is for something narrower and unrelated — anyone who wants a throwaway DATABASE_URL for a prototype or a test run without creating a Neon account first. The logging skill could apply to any project regardless of database.

READ THE FULL ANALYSIS＋

Neon's own warning, not ours. The README says plainly that the MCP server is meant for local development and IDE integration only, and recommends against production use, because a natural-language request can create, delete, or migrate a database before a person has fully reviewed what it will do.

One skill we could not verify. Our data marks logging-best-practices' dependency requirements as unverified, unlike claimable-postgres' confirmed local-tool footprint, so treat that skill's setup instructions as read from its file rather than independently confirmed.