Cursor Neon MCP not connecting to Vercels' linked Neon DB

I

The remote MCP server uses Neon's auth flow to connect. I don't think this will work for an Vercel-managed Neon project. You could try a local MCP server installation and supply an Org-scoped Neon API key:
Local MCP server install instructions: https://neon.com/docs/ai/neon-mcp-server#local-mcp-server
Org-scoped Neon API key: https://neon.com/docs/manage/api-keys#create-an-organization-api-key

Please let us know if it works for you or not.

V

verbal-lime•6/3/25, 3:21 AM

I'm having the same issue, tried remote server and then local. Everything seems to be fine but agent don't find project or anything else. @Daniel

I

instant-harlequin•6/3/25, 9:44 AM

Hi, I just tested this. I was able to access projects in my Vercel org using an organization-scoped API key and a local MCP server setup. When I changed my MCP server configuration from remote to local, it didn't work until I restarted Cursor and refreshed the MCP server.

V

verbal-lime•6/3/25, 2:08 PM

@Thiago M @fury Did you try using a prompt with your org id?

list all projects in organization {orgID}

list all projects in organization {orgID}

list all projects in organization {orgID}

list all projects in organization {orgID}

The

listProject

listProject

listProject

listProject tool takes an optional orgId as input. The LLM should be able to forward that to MCP if you include it in prompt. With OAuth authentication you should have access to organization projects as well. This might not work when running MCP locally because of user-scoped API keys.

I

instant-harlequin•6/5/25, 10:20 AM

@shriidhar I am assuming that the auth flow uses a personal Neon account (like the Neon CLI) — and that account would have to be a member of the org to access org projects. Someone coming from Vercel would not have a personal Neon account, so I assume they would have to use a local MCP installation with an org-scoped API key. That's how I was able to access projects in my Vercel org via MCP.

V

verbal-lime•6/5/25, 2:34 PM

@fury If it worked on smithery and not with

npx

npx

npx

npx that would probably mean you are running older (cached) version of package.

Please try with

@latest

@latest

@latest

@latest to install latest version.

{
  "Neon": {
    "command": "npx",
    "args": ["-y", "@neondatabase/mcp-server-neon@latest", "start", "<api_key>"]
  },
}

{
  "Neon": {
    "command": "npx",
    "args": ["-y", "@neondatabase/mcp-server-neon@latest", "start", "<api_key>"]
  },
}

{
  "Neon": {
    "command": "npx",
    "args": ["-y", "@neondatabase/mcp-server-neon@latest", "start", "<api_key>"]
  },
}

{
  "Neon": {
    "command": "npx",
    "args": ["-y", "@neondatabase/mcp-server-neon@latest", "start", "<api_key>"]
  },
}

can it be that @neondatabase/mcp-server-neon is not allowing org-keys?

It should work just fine with org-keys, by listing just org-projects. There is no specific logic in here for Smithery or local.

V

verbal-lime•6/11/25, 10:59 AM

Tt looks like indeed a bug in latest version while identifying user accounts for one-of-new feature. One of the API call fails with org-api-key with insufficient permissions. This has been fixed and awaiting review. Will soon publish new version

V

verbal-lime•6/16/25, 11:54 AM

The new version with the fix has been published today. Please feel free to give it try and let me if that works.

{
  "Neon": {
    "command": "npx",
    "args": ["-y", "@neondatabase/mcp-server-neon@latest", "start", "<org_api_key>"]
  },
}

{
  "Neon": {
    "command": "npx",
    "args": ["-y", "@neondatabase/mcp-server-neon@latest", "start", "<org_api_key>"]
  },
}

{
  "Neon": {
    "command": "npx",
    "args": ["-y", "@neondatabase/mcp-server-neon@latest", "start", "<org_api_key>"]
  },
}

{
  "Neon": {
    "command": "npx",
    "args": ["-y", "@neondatabase/mcp-server-neon@latest", "start", "<org_api_key>"]
  },
}

Cursor Neon MCP not connecting to Vercels' linked Neon DB

Similar Threads

Similar Threads

Similar Threads