Neon Auth MCP OAuth

Created By
andrelandgrafa year ago
PoC of an MCP server in a Next.js app with Neon Auth and custom OAuth flow for MCP.
Overview

what is Neon Auth MCP OAuth?

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

how to use Neon Auth MCP OAuth?

To use this project, add the provided MCP configuration to your application (e.g., Cursor, Windsurf, Claude Desktop) and replace the example URL with your local development server URL.

key features of Neon Auth MCP OAuth?

  • Custom OAuth flow implementation
  • Integration with Next.js and Neon Auth
  • Utilizes Upstash Redis for state management

use cases of Neon Auth MCP OAuth?

  1. Implementing custom authentication flows in web applications.
  2. Integrating OAuth with Next.js applications.
  3. Using Redis for session management in authentication processes.

FAQ from Neon Auth MCP OAuth?

  • What technologies are used in this project?

The project uses Next.js, Neon, Upstash Redis, and Neon Auth.

  • How can I set up the project locally?

Follow the setup instructions to configure Neon and deploy to Vercel, then set up Redis Upstash.

  • Is this project production-ready?

This is a proof of concept and may require further development for production use.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
andrelandgraf
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Voyei

2 hours ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago