Neon MCP Server bridges natural language AI assistants with Neon Postgres databases, translating conversational requests into Neon API operations. Key capabilities: - Create and manage Neon projects, database branches, and Postgres instances through natural language commands - Execute database schema migrations using Neon's branching features initiated via conversational prompts - Run SQL queries and retrieve database information without manual SQL writing - Access project summaries and database metadata across your Neon organization - Integrates with Claude Code, Cursor, and other MCP-compatible AI coding assistants

Neon MCP Server

[](https://cursor.com/en-US/install-mcp?name=Neon&config=eyJ1cmwiOiJodHRwczovL21jcC5uZW9uLnRlY2gvbWNwIn0%3D)

Neon MCP Server is an open-source tool that lets you interact with your Neon Postgres databases 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:

For example, in Claude Code, or any MCP Client, you can use natural language to accomplish things with Neon, such as:

> [!WARNING] > Neon MCP Server Security Considerations > The Neon MCP Server grants powerful database management capabilities through natural language requests. Always review and authorize actions requested by the LLM before execution. Ensure that only authorized users and applications have access to the Neon MCP Server. > > The Neon MCP Server is intended for local development and IDE integrations only. We do not recommend using the Neon MCP Server in production environments. It can execute powerful operations that may lead to accidental or unauthorized changes. > > For more information, see MCP security guidance →.

Setting up Neon MCP Server

There are a few options for setting up the Neon MCP Server:

1. Quick Setup with API Key (Cursor, VS Code, and Claude Code): Run neonctl@latest init to automatically configure Neon's MCP Server, agent skills, and VS Code extension with one command. 2. Remote MCP Server (OAuth Based Authentication): Connect to Neon's managed MCP server using OAuth for authentication. This method is more convenient as it eliminates the need to manage API keys. Additionally, you will automatically receive the latest features and improvements as soon as they are released. 3. Remote MCP Server (API Key Based Authentication): Connect to Neon's managed MCP server using API key for authentication. This method is useful if you want to connect a remote agent to Neon where OAuth is not available. Additionally, you will automatically receive the latest features and improvements as soon as they are released.

Prerequisites

For development, you'll also need Bun installed.

Option 1. Quick Setup with API Key

Don't want to manually create an API key?

Run neonctl@latest init to automatically configure Neon's MCP Server with one command:

npx neonctl@latest init

This works with Cursor, VS Code (GitHub Copilot), and Claude Code. It will authenticate via OAuth, create a Neon API key for you, and configure your editor automatically.

Option 2. Remote Hosted MCP Server (OAuth Based Authentication)

Connect to Neon's managed MCP server using OAuth for authenticat