Specific implementation researched
Neon MCP
Implementation, permissions and documented client compatibility.
A directory listing or verification does not replace a security audit. No installation is triggered automatically here. Do not enter API keys in public forms.
What is specifically documented?
- Connected service
- Neon
- Publisher
- Neon
- Origin
- Officially from the named publisher
- Deployment mode
- Remote
- Transport
- HTTP
- Authentication
- OAuth or an API key as a bearer token.
- Read capabilities
- Inspect projects and schemas · Run SELECT queries · Read branch and database information
- Write capabilities
- Manage projects and branches · Execute migrations and data changes
- Permissions
- readonly=true, project_id, Postgres role and tool categories limit access; all tool categories are available by default.
- Required plan
- No confirmed information
- Additional costs
- No confirmed information
- Maintenance status
- No confirmed information
- Review date
- 11/10/2026
Support by client
Documented setup is not an independent functional test. General MCP support does not imply full compatibility.
| Client | Status | Source |
|---|---|---|
| Claude Desktop | Setup documented | Documentation ↗ |
| Claude Code | Not verified | — |
| Claude Web | Setup documented | Documentation ↗ |
| Cursor | Not verified | — |
Sources & implementation
Neon MCP Server overview - Neon Docs ↗Retrieved on 11/10/2026. Provider statements, not a security audit.
Implementation: https://mcp.neon.tech/mcp