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
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago