Neon Extension

This tutorial covers how to add the Neon MCP Server as a Goose extension to interact with your Neon Postgres databases and manage your projects, branches, and more.

Neon offers two versions of the MCP server:

1. Remote MCP server hosted by Neon, which redirects you to neon.com to sign in to your Neon account.
2. Local MCP server that you can run on your own machine using an API key to connect with a specific organization or your personal account.

Security Note

The Neon MCP Server grants powerful database management capabilities and is intended for local development only - always review LLM-requested actions before execution and avoid using in production environments.

Configuration

Neon Remote MCP

TLDR

Goose Desktop

Use Add custom extension in Settings → Extensions to add a Streamable HTTP extension type with:

Goose CLI

Use goose configure to add a Remote Extension (Streaming HTTP) extension type with:

Endpoint URL

https://mcp.neon.tech/mcp

OAUTH FLOW

An OAuth window will open in your browser. Follow the prompts to authorize access to your Neon account.

Goose Desktop

1. Click the button in the top-left to open the sidebar
2. Click Extensions
3. Click Add custom extension
4. On the Add custom extension modal, enter the following:
   • Extension Name: Neon
   • Type: Streamable HTTP
   • Endpoint: https://mcp.neon.tech/mcp
5. Click Add Extension to save the extension
6. Navigate to the chat

Goose CLI

1. Run the configure command:

goose configure

2. Choose to add a Remote Extension (Streaming HTTP)

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension
│
◆  What type of extension would you like to add?
│  ○ Built-in Extension 
│  ○ Command-line Extension
│  ○ Remote Extension (SSE)
│  ● Remote Extension (Streaming HTTP) (Connect to a remote extension via MCP Streaming HTTP)
└

3. Give your extension a name

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension
│
◇  What type of extension would you like to add?
│  Remote Extension (Streaming HTTP)
│
◆  What would you like to call this extension?
│  neon-mcp-remote
└

4. Enter the endpoint URI

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension
│
◇  What type of extension would you like to add?
│  Remote Extension (Streaming HTTP)
│
◇  What would you like to call this extension?
│  neon-mcp-remote
│
◆  What is the Streaming HTTP endpoint URI?
│  https://mcp.neon.tech/mcp
└

5. Enter the number of seconds Goose should wait for actions to complete before timing out. Default is 300 seconds

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension
│
◇  What type of extension would you like to add?
│  Remote Extension (Streaming HTTP)
│
◇  What would you like to call this extension?
│  neon-mcp-remote
│
◇  What is the Streaming HTTP endpoint URI?
│  https://mcp.neon.tech/mcp
│
◆  Please set the timeout for this tool (in secs):
│  300
└

6. Choose to add a description. If you select Yes, you'll be prompted to enter a description for the extension

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension
│
◇  What type of extension would you like to add?
│  Remote Extension (Streaming HTTP)
│
◇  What would you like to call this extension?
│  neon-mcp-remote
│
◇  What is the Streaming HTTP endpoint URI?
│  https://mcp.neon.tech/mcp
│
◇  Please set the timeout for this tool (in secs):
│  300
│
◆  Would you like to add a description?
│  No
└

7. Choose No when asked to add custom headers

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension
│
◇  What type of extension would you like to add?
│  Remote Extension (Streaming HTTP)
│
◇  What would you like to call this extension?
│  neon-mcp-remote
│
◇  What is the Streaming HTTP endpoint URI?
│  https://mcp.neon.tech/mcp
│
◇  Please set the timeout for this tool (in secs):
│  300
│
◇  Would you like to add a description?
│  No
│
◆  Would you like to add custom headers?
│  No
└  Added neon-mcp-remote extension

Neon Local MCP

TLDR

Goose Desktop

Launch the installer

Goose CLI

Command

npx -y @neondatabase/mcp-server-neon start <YOUR_NEON_API_KEY>

No environment variables are needed.

Prerequisites

• Node.js (v18.0.0 or higher) installed on your system to run this command, as it uses npx
• Neon API key to authenticate the Neon MCP Server with your Neon account. You can create one from the Neon Console under your Profile settings. Refer to the Neon documentation on API Keys for detailed instructions.

Goose Desktop

1. Launch the installer
2. Click OK to confirm the installation
3. Click the button in the top-left to open the sidebar
4. Navigate to the chat

Goose CLI

1. Run the configure command:

goose configure

2. Choose to add a Command-line Extension.

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension (Connect to a new extension)
│
◆  What type of extension would you like to add?
│  ○ Built-in Extension 
│  ● Command-line Extension (Run a local command or script)
│  ○ Remote Extension 
└

3. Give your extension a name.

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension (Connect to a new extension)
│
◇  What type of extension would you like to add?
│  Command-line Extension 
◆  What would you like to call this extension?
│  Neon MCP
└

4. Enter the command to run when this extension is used.

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension (Connect to a new extension)
│
◇  What type of extension would you like to add?
│  Command-line Extension 
│
◇  What would you like to call this extension?
│  Neon MCP
│
◆  What command should be run?
│  npx -y @neondatabase/mcp-server-neon start <YOUR_NEON_API_KEY>
└

5. Enter the number of seconds Goose should wait for actions to complete before timing out. Default is 300 seconds.

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension (Connect to a new extension) 
│
◇  What type of extension would you like to add?
│  Command-line Extension 
│
◇  What would you like to call this extension?
│  Neon MCP
│
◇  What command should be run?
│  npx -y @neondatabase/mcp-server-neon start <YOUR_NEON_API_KEY>
│
◆  Please set the timeout for this tool (in secs):
│  300
└

6. Choose to add a description. If you select Yes, you’ll be prompted to enter a description for the extension.

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension (Connect to a new extension)
│
◇  What type of extension would you like to add?
│  Command-line Extension 
│
◇  What would you like to call this extension?
│  Neon MCP
│
◇  What command should be run?
│  npx -y @neondatabase/mcp-server-neon start <YOUR_NEON_API_KEY>
│
◇  Please set the timeout for this tool (in secs):
│  300
│
◆  Would you like to add a description?
│  No
└

7. Choose No when asked to add environment variables

┌   goose-configure 
│
◇  What would you like to configure?
│  Add Extension (Connect to a new extension) 
│
◇  What type of extension would you like to add?
│  Command-line Extension 
│
◇  What would you like to call this extension?
│  Neon MCP
│
◇  What command should be run?
│  npx -y @neondatabase/mcp-server-neon start <YOUR_NEON_API_KEY>
│
◇  Please set the timeout for this tool (in secs):
│  300
│
◇  Would you like to add a description?
│  No
│
◆  Would you like to add environment variables?
│  No
└  Added Neon MCP extension

For all setup and configuration options, see the official Neon MCP Server documentation.

Example Usage 1

Get an overview of all your Neon database projects and their configurations.

Goose Prompt

List my Neon projects

Goose Output

I'll help you list your Neon projects using the neon__list_projects tool. By default, it will show the first 10 projects.

Here are your Neon projects:

1. laravel-test (ID: mute-mountain-08595850)
- Region: AWS US East 2
- Created: July 23, 2025
- PostgreSQL: v17

2. rls-test (ID: noisy-hill-99207787)
- Region: AWS US East 2
- Created: July 20, 2025
- PostgreSQL: v17

3. neon-auth-test (ID: rapid-pond-81053507)
- Region: Azure East US 2
- Created: July 7, 2025
- PostgreSQL: v17

4. saas-starter-kit-nextjs (ID: misty-poetry-78149700)
- Region: AWS US West 2
- Created: June 23, 2025
- PostgreSQL: v17
- Note: Has logical replication enabled

5. neon-auth-mcp-oauth (ID: gentle-base-21700263)
- Region: AWS US West 2
- Created: June 4, 2025
- PostgreSQL: v17

All projects are running PostgreSQL 17 and have autoscaling configured between 1-2 compute units. Would you like more detailed information about any specific project?

Example Usage 2

Discover what tables and schemas exist within a specific project.

Goose Prompt

What tables do I have in my neon-auth-mcp-oauth project?

Goose Output

In your neon-auth-mcp-oauth project, there is one table:

users_sync in the neon_auth schema

Example Usage 3

Run queries against your database tables to retrieve and analyze your data.

Goose Prompt

Count the rows in the users_sync table.

Goose Output

I'll count the rows in the neon_auth.users_sync table using a COUNT query.

Total Records: 1 row
Table Location: Schema neon_auth, Table users_sync
Project: neon-auth-mcp-oauth (Project ID: gentle-base-21700263)
Content: Contains one user record