Can AI agents automate Neon?

Neon serverless Postgres is automatable today through a public REST API, an official CLI, and a first-party hosted MCP server. The Neon API at https://console.neon.tech/api/v2 manages projects, branches, databases, roles, computes, API keys, and related resources with a Bearer API key. Keys are personal, organization-scoped, or project-scoped; the secret is shown once. The API documents 169 endpoints across 19 resources. Official management SDKs exist for TypeScript (@neon/sdk) and Python. The neon CLI authenticates with NEON_API_KEY or --api-key, supports --output json|yaml|table, and is documented for agents, CI, and scripts. The hosted MCP server at https://mcp.neon.tech/mcp uses Streamable HTTP with OAuth or an API key. Tools cover projects, branches, schema, SQL, Data API, Auth, functions, storage, logs, and docs. URL parameters support readonly, projectId, and category filters. Local stdio package @neondatabase/mcp-server-neon is deprecated. The older /sse transport is deprecated and scheduled to return 410 on or after 2026-10-01. Neon recommends MCP for development and testing, not production data. If IP Allow is enabled, add 34.192.103.46 and 23.22.233.166. Computer-use viability is unassessed. API and CLI both score 8; API is the best path because it does not require a local CLI install and is not limited to development data.

Best path today: api · Overall automatability: 8/10