A side-by-side look at the LeadMCP and MCP Server Neon MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose LeadMCP for databases work; choose MCP Server Neon for databases as a local process. You can also run both side by side in one mcpServers block.
NEON_API_KEY.projects, branches, endpoints.Rows where the two servers differ are marked.
| Spec | L LeadMCP | |
|---|---|---|
| Category | Databases | Databases |
| Quality signal | 37/100 · Fair | 67/100 · Great |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | Not declared | OAuth 2.0 |
| Pricing | Not declared | Freemium |
| Required env vars | None listed | NEON_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | 653 |
| Directory activity | 0 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 80 |
| Full listing | View LeadMCP | View MCP Server Neon |
No tool names declared yet. Check the project README from the listing page.
projectsbranchesendpointssnapshotsschemaqueryingneon_authdata_apiobservabilitydocsfunctionsstoragePaste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
No confirmed install command for LeadMCP yet — follow the setup steps linked from its listing page rather than a guessed package name.
{
"mcpServers": {
"neondatabase-mcp-server-neon": {
"command": "npx",
"args": [
"-y",
"neon@latest"
],
"env": {
"NEON_API_KEY": "YOUR_NEON_API_KEY_HERE"
}
}
}
}