NeonCAUTION
MCP server for interacting with Neon Management API and databases
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
[](https://cursor.com/en-US/install-mcp?name=Neon&config=eyJ1cmwiOiJodHRwczovL21jcC5uZW9uLnRlY2gvbWNwP2NhdGVnb3J5PXByb2plY3RzJmNhdGVnb3J5PWJyYW5jaGVzJmNhdGVnb3J5PWVuZHBvaW50cyZjYXRlZ29yeT1xdWVyeWluZyZjYXRlZ29yeT1zY2hlbWEifQ%3D%3D) [](https://kiro.dev/launch/mcp/add?name=Neon&config=%7B%22url%22%3A%22https%3A%2F%2Fmcp.neon.tech%2Fmcp%3Fcategory%3Dprojects%26category%3Dbranches%26category%3Dendpoints%26category%3Dquerying%26category%3Dschema%22%7D)
Neon MCP Server is an open-source tool that lets you interact with your Lakebase Postgres databases on Neon in natural language.
[](https://opensource.org/licenses/MIT)
The Model Context Protocol (MCP) is a standardized protocol designed to manage context between large language models (LLMs) and external systems. This repository provides a remote MCP Server for Neon.
Neon's MCP server acts as a bridge between natural language requests and the Neon API. Built upon MCP, it translates your requests into the necessary API calls, enabling you to manage tasks such as creating projects and branches, running queries, and performing database migrations seamlessly.
Some of the key features of the Neon MCP server include:
- Natural language interaction: Manage Neon databases using intuitive, conversational commands.
- Simplified database management: Perform complex actions
55b970b3826cOBSERVED · 2026-09-30Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control. Replace the environment placeholders with a token scoped to the least it needs.
claude mcp add mcp-server-neon --env ANALYTICS_WRITE_KEY=${ANALYTICS_WRITE_KEY} --env CLIENT_SECRET=${CLIENT_SECRET} --env OAUTH_DATABASE_URL=${OAUTH_DATABASE_URL} --env UPSTREAM_OAUTH_HOST=${UPSTREAM_OAUTH_HOST} -- npx -y @neondatabase/[email protected]{
"mcpServers": {
"mcp-server-neon": {
"command": "npx",
"args": [
"-y",
"@neondatabase/[email protected]"
],
"env": {
"ANALYTICS_WRITE_KEY": "${ANALYTICS_WRITE_KEY}",
"CLIENT_SECRET": "${CLIENT_SECRET}",
"OAUTH_DATABASE_URL": "${OAUTH_DATABASE_URL}",
"UPSTREAM_OAUTH_HOST": "${UPSTREAM_OAUTH_HOST}"
}
}
}
}Trust audit
CAUTIONgrade F · trust 58/100 Install with care. The audit found things worth knowing before you trust its output.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | WARN |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (5 observation(s))
- Network
- declared (2 observation(s))
- Shell
- none-observed
- Dependencies
- pinned
- Secrets in source
- found
Findings (25)
.claude/skills/claimable-postgres
.claude/skills/logging-best-practices
logger.info('OAuth token found', { clientId: token.client.id });connectionString: 'postgresql://neondb_owner:secret@host/neondb',
connection_uri: 'postgresql://neondb_owner:secret@host/neondb',
connectionString: 'postgresql://neondb_owner:secret@host/neondb',
{ connection_uri: 'postgresql://neondb_owner:secret@host/neondb' },uri: 'postgresql://owner:[email protected]/neondb',
password: 'super-secret-smtp-from-upstream',
.env.test.example
.prettierignore
import '../../../mcp/sentry/instrument';
import { NEON_HANDLERS } from '../../../mcp/tools/index';} from '../../../mcp/tools/handlers/docs';
import { createNeonClient } from '../../../mcp/server/api';import pkg from '../../../package.json';
To verify a local MCP server against the real Neon API, start it with `NEON_API_KEY` in its environment (for example, `pnpm exec next dev --port 3031`), then use `npx mcporter` from an untracked tempo
export const DOCS_FIXTURE_INDEX_URL = `http://127.0.0.1:${DOCS_FIXTURE_PORT}${DOCS_FIXTURE_PATH}`;page.getByText('http://127.0.0.1:55667/callback'),redirect_uris: ['http://127.0.0.1:55667/callback'],
const response = await request.get(`http://127.0.0.1:${port}${path}`, {const credentials = atob(authorization.replace(/^Basic\s+/i, ''));
const credentials = atob(authorization.replace(/^Basic\s+/i, ''));
- **`write`**: Full access including create/delete operations
# Full access
Gates applied: no_behavioural_pass.
55b970b3826cfull audit observations/trust-audit/mcp-server/neondatabase-labs__neon-1.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-09-30 | 55b970b3826c | CAUTION | F | 58 | first audit |
Questions
What is the Neon MCP server?
MCP server for interacting with Neon Management API and databases
Is Neon safe to connect to an agent?
With care. The audit graded it F (58/100) and found 25 things worth knowing before you trust this server, listed below with the exact line each was found on.
What credentials does Neon need?
It reads ANALYTICS_WRITE_KEY, CLIENT_SECRET, OAUTH_DATABASE_URL and UPSTREAM_OAUTH_HOST from the environment. Give it a token scoped to the least it needs — an agent that can be talked into calling a tool can be talked into calling it with your credentials.
How does Neon run?
It speaks streamable-http, so it runs as a service you connect to over the network. It is published on npm as @neondatabase/mcp-server-neon at 1.0.0.
How current is this page?
The grade is for one exact copy of the source (55b970b3826c), read on 2026-09-30. The repository is watched and re-audited when it changes.