mcp/neon

by neondatabaseio.github.neondatabase/mcp-server-neon

MCP server for interacting with Neon Management API and databases

  • Remote endpoint
  • MIT

Uptime

Checked  · every day

67.56%from 5 days of checks

Up without downtime on 3 of 5 days with data; down 2074 minutes in all, the longest 1187 minutes on 4 November.

  • No downtime
  • Degraded
  • Down over 5 minutes
  • No data
  • Not checked yet

How far each check got

  • Reached the address 100%
  • Completed the handshake 0.0%
  • Listed its tools 0.0%
Every day
DayResultChecksMedian
4 Nov (today)Down 1187 minutes1–
3 NovDown 887 minutes13of 1–
2 NovNo downtime1of 1–
1 NovNo downtime1of 1–
31 OctNo downtime1–

A failure counts as down time only when a second check five minutes later fails too. How we check

Connect to the publisher's own endpoint

Add to ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project):

{
  "mcpServers": {
    "mcp-server-neon": {
      "url": "https://mcp.neon.tech/sse"
    }
  }
}

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server mcp/neon (`io.github.neondatabase/mcp-server-neon`)

Its page: https://plug.directory/servers/io.github.neondatabase/mcp-server-neon

It runs on the publisher's servers; the client connects to its URL.

Use the section for the person's client.

## Claude Desktop

Paste into Settings › Connectors › Add custom connector:

```text
https://mcp.neon.tech/sse
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport sse mcp-server-neon https://mcp.neon.tech/sse
```

## Cursor, Devin Desktop, LM Studio, Gemini CLI, oterm, ECA

Merge into the place for the person's client:

- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project

```json
{
  "mcpServers": {
    "mcp-server-neon": {
      "url": "https://mcp.neon.tech/sse"
    }
  }
}
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "mcp-server-neon": {
      "type": "sse",
      "url": "https://mcp.neon.tech/sse"
    }
  }
}
```

## Zed

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Cline, AnythingLLM, Augment Code

Merge into the place for the person's client:

- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)

```json
{
  "mcpServers": {
    "mcp-server-neon": {
      "type": "sse",
      "url": "https://mcp.neon.tech/sse"
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "mcp-server-neon"
    type: sse
    url: "https://mcp.neon.tech/sse"
```

## Goose

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Codex

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## mcp-client-cli, TUUI, BoltAI, Bob Shell, Kiro, Kiro CLI

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Agenvoy

This server's endpoint speaks only SSE, which this client's documentation does not list among its transports; use another client for it.

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "mcp-server-neon": {
      "url": "https://mcp.neon.tech/sse"
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

From GitHub MCP Registry, Docker Hub, Docker MCP Catalog, Docker MCP Registry. Report a problem