Neon Auth MCP OAuth

Name: Neon Auth MCP OAuth
Author: andrelandgraf

@andrelandgraf

リポジトリホームページ

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

基本情報

カテゴリ

開発者ツール

ランタイム

node

トランスポート

stdio

公開者

andrelandgraf

設定

以下の設定を使って、このサーバーを MCP 対応クライアントに追加してください。

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

ツール

ツールは検出されませんでした

ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。

概要

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

FAQ from Neon Auth MCP OAuth

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.

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).