MCP.so
Sign In

Neon Auth MCP OAuth

@andrelandgraf

Basic information

Category

Developer Tools

Transports

stdio

Author

andrelandgraf

About Neon Auth MCP OAuth

PoC of an MCP server in a Next.js app with Neon Auth and custom OAuth flow for MCP.

#neon-auth#oauth#nextjs

Neon Auth MCP OAuth config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "echo": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://neon-auth-mcp-oauth-6zf3o859s-andrelandgraf.vercel.app"
      ]
    }
  }
}

Neon Auth MCP OAuth tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

Fetch the live tool list by running this server in a temporary sandbox using the button above.

Overview

What is Neon Auth MCP OAuth?

A proof-of-concept implementation of a custom MCP OAuth flow built with Next.js, Neon, Upstash Redis, and Neon Auth. It is designed for developers who want to experiment with MCP authentication using Neon Auth and OAuth.

How to use Neon Auth MCP OAuth?

Add the provided MCP configuration to Cursor, Windsurf, Claude Desktop, or any MCP client. For local development, replace the URL in the config with http://localhost:3000/api/v1/mcp and run npm run dev.

Key features of Neon Auth MCP OAuth

  • Custom MCP OAuth flow implementation
  • Built with Next.js, Neon, Upstash Redis, and Neon Auth
  • Deployable to Vercel with Upstash Redis integration
  • Debugging support via MCP Inspector
  • Includes a development server for local testing

Use cases of Neon Auth MCP OAuth

  • Experimenting with MCP OAuth authentication in a Next.js environment
  • Integrating Neon Auth with MCP clients like Cursor, Windsurf, or Claude Desktop
  • Prototyping custom OAuth workflows for MCP servers
  • Learning how to combine Neon, Upstash Redis, and Neon Auth for MCP

Frequently asked questions

1

What is this project?

It is a proof of concept (PoC) for a custom MCP OAuth flow using Next.js, Neon, Upstash Redis, and Neon Auth.

2

What are the dependencies and runtime requirements?

You need to set up a Neon database and Neon Auth, deploy to Vercel, and configure Upstash Redis via the Vercel Upstash Integration. Environment variables are required (see `./lib/config.ts`).

3

How do I reset auth state if I run into issues?

Run `rm -rf ~/.mcp-auth` to clear stored authentication data from the `mcp-remote` package. MCP auth is noted as still flaky.

4

Can I run this locally?

Yes, clone the repository, set up the environment, and run `npm run dev`. Use `npm run playground` to start the MCP Inspector for debugging.

5

What transports or authentication does it use?

It uses a custom OAuth flow over HTTP/HTTPS (the MCP server endpoint is `/api/v1/mcp`). Authentication is handled via Neon Auth and OAuth tokens.

Comments

More Developer Tools MCP servers