How to Connect Neon to an AI Agent
Auth setup
Remote (recommended): claude mcp add --transport http neon [remote-mcp-url]. Browser OAuth flow on first use. Local: 1. Get API key from console.neon.tech/settings/api-keys. 2. claude mcp add neon -- npx -y @neondatabase/mcp-server-neon (set NEON_API_KEY env).
Key facts
| Base URL | https://console.neon.tech/api/v2/ (control plane) + postgres:// connection strings (data plane) |
|---|
| API version | v2 (control plane) |
|---|
| Auth | Two modes: (1) Remote managed MCP with OAuth (recommended, no API key management) or (2) Local with Neon API key (NEON_API_KEY env var, generated at console.neon.tech/settings/api-keys). |
|---|
| Scopes | Account-level (API keys currently grant full account access). |
|---|
| Request body | application/json |
|---|
| Pagination | Cursor-based: `limit` + `cursor` query params for list endpoints. |
|---|
| Rate limit | Control plane: 700 requests/minute per API key. Data plane: bound by compute size (Free tier: 0.25 CU = ~100 connections via pooled URL). |
|---|
| Error format | JSON: {"code":"...","message":"..."} for control plane. Standard PostgreSQL errors for data plane. |
|---|
Key endpoints
| Method | Path | Description |
|---|
POST | /projects | Create a Neon project (creates a primary branch and compute) |
GET | /projects/{project_id}/branches | List branches (Neon supports Git-like DB branching) |
POST | /projects/{project_id}/branches | Create a new branch from an existing branch |
GET | /projects/{project_id}/endpoints | List compute endpoints for a project |
POST | /projects/{project_id}/databases | Create a database within a project |
Quickstart
GET https://console.neon.tech/api/v2/projects
Authorization: Bearer {neon_api_key}
Response: {"projects":[{"id":"quiet-snowflake-123","name":"My App","region_id":"aws-us-east-1","created_at":"..."}]}
Agent pitfalls & tips
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
- [object Object]
Source: curated by KanseiLink from official documentation (docs) and registry checks. Last reviewed: 2026-06-08. Specs change — verify against the official docs before production use.
Frequently Asked Questions
What is Neon's AEO score?
▼
Neon has an AEO score of 0.90 and is rated AA (Strong agent support with minor gaps). AEO (Agent Engine Optimization) measures how well a SaaS service works with AI agents. Scores range from 0.00 to 1.00, with grades from AAA (best) to D (not agent-ready).
Is Neon AI-agent-ready?
▼
Neon is currently connectable for AI agent use. Third-party MCP integrations are available for this service. For detailed connection guides, auth setup, and known pitfalls, use the KanseiLink MCP tool.
How does Neon compare to other Database services?
▼
In the Database category, Neon is rated AA. KanseiLink evaluates services based on MCP availability, API quality, documentation, auth-guide clarity, and integration recipe availability (methodology published). Visit the full rankings at kansei-link.com to see how Neon compares.
How can I integrate Neon with an AI agent?
▼
The fastest way to integrate Neon with an AI agent is through KanseiLink MCP. Install it with: npx @kansei-link/mcp-server — then use the search_services and get_service_detail tools to get the current auth setup, endpoints, rate limits, and agent-specific tips. This data is kept fresh from registry checks, curated official-doc guides, and agent reports.
How do I authenticate with Neon?
▼
Two modes: (1) Remote managed MCP with OAuth (recommended, no API key management) or (2) Local with Neon API key (NEON_API_KEY env var, generated at console.neon.tech/settings/api-keys). Setup: Remote (recommended): claude mcp add --transport http neon [remote-mcp-url]. Browser OAuth flow on first use. Local: 1. Get API key from console.neon.tech/settings/api-keys. 2. claude mcp add neon -- npx -y @neondatabase/mcp-server-neon (set NEON_API_KEY env).
What are Neon's API rate limits?
▼
Control plane: 700 requests/minute per API key. Data plane: bound by compute size (Free tier: 0.25 CU = ~100 connections via pooled URL).