Project lifecycle
List, describe, create, and delete Neon projects with management tools.
Documentation ↗MCP server / databases / source-linked
Neon MCP
Neon MCP is Neon’s hosted server for project and Postgres management. The current endpoint supports Streamable HTTP, OAuth consent, project/category selectors, and read-only grants; an API-key header is available for automation. Its useful distinction is that categories expose concrete scopes such as branches, endpoints, schema, querying, and observability.
Before you choose.
Identify the implementation and the job it supports.
Neon MCP is Neon’s hosted server for project and Postgres management. The current endpoint supports Streamable HTTP, OAuth consent, project/category selectors, and read-only grants; an API-key header is available for automation. Its useful distinction is that categories expose concrete scopes such as branches, endpoints, schema, querying, and observability.
Setup and connection.
The documented interface, authentication and installation path.
- Connection / transport
- Streamable HTTP; legacy SSE endpoint remains for older clients
- Authentication
- OAuth with read/write consent or a Neon API key in Authorization for automation.
Use npx add-mcp with categories or add the hosted URL to mcp.json; authenticate in the browser, then restart or refresh the client. Prefer projectId/category/read-only selectors.
Setup reference ↗Documented setup example. Review the source and credentials before running; this command was not executed for this article.
npx add-mcp "https://mcp.neon.tech/mcp?category=projects&category=branches&category=endpoints&category=querying&category=schema"What it actually exposes.
Concrete capabilities with maintainer sources.
Branch and compute operations
Work with branches, Postgres roles/databases, endpoints, snapshots, and connection strings.
Documentation ↗Schema and querying
Inspect schemas, compare database structure, query data, and access performance/observability categories.
Documentation ↗Evidence and method.
What was checked and what was not tested.
HOW
Source method
Public maintainer documentation and repositories. This is not a hands-on product review.
WHEN
Last checked 2026-10-01
Setup examples are documented examples. Suggested trials and comparison advice are editorial guidance.
Sources support the adjacent factual statements. A source review does not establish uptime, performance, security or current account eligibility. Read the editorial policy.
Try a specific task.
A bounded evaluation you can reproduce in your own environment.
Branch-first migration review
Suggested evaluation, not an observed test result.
- Connect only the target Neon project and request read-only schema/querying categories.
- Ask the agent to compare branches and propose a migration impact report.
- Review the SQL and apply changes on a branch before merging.
What to inspect: A branch-scoped change plan with explicit schema impact and rollback context. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Workflow reference ↗Permissions and limitations.
Read these constraints before granting access.
Write operations remain possible unless the OAuth grant or readonly selector excludes them; deleting projects and migrations deserve explicit human approval.
Boundary reference ↗SSE is deprecated and should only be used when a client lacks Streamable HTTP support.
Boundary reference ↗Decide by workflow.
Make the expected output explicit before you connect.
A branch-scoped change plan with explicit schema impact and rollback context. Record the client, selected scope, date, and approval checkpoint so readers can reproduce the decision. Keep the source links beside each claim when publishing the record. Proposed workflow; not tested by clawbot.ai.
Keep the task inputs, tool calls, output and any errors together when you evaluate. The trial above is a proposal, not a recorded result.
Compare the alternatives.
Specific reasons to choose another route, with the tradeoff shown.
| Alternative | Choose it when | Tradeoff |
|---|---|---|
| Supabase MCP | Choose when project debugging, Edge Functions, and Supabase docs are part of the workflow. | Supabase’s feature groups differ from Neon’s branch/endpoint-first controls. Documentation ↗ |
| Google Gen AI Toolbox | Choose for self-hosted access across many database engines. | Neon MCP is faster to start but vendor-specific. Documentation ↗ |
Questions before setup.
Answers specific to this implementation.
Can I use this without a local server?
Yes; the hosted endpoint uses OAuth and needs no local installation.
Documentation ↗
How do I reduce tools?
Use category, projectId, and readonly selectors in the MCP URL or consent screen.
Documentation ↗
Source trail.
Maintainer documentation used in this record.