Midnight + Next.Js MCP
Wire Midnight blockchain contracts and Next.js dApp scaffolding into Claude Code or Cursor without juggling separate docs and CLIs.
Overview
Midnight + Next.js MCP is a Build-phase MCP server that unifies Midnight blockchain development helpers with Next.js dApp workflows for coding agents.
What is this MCP server?
- Single stdio MCP server for Midnight blockchain dev and Next.js dApps
- npm launch via npx with optional Node --experimental-vm-modules flag
- Optional MIDNIGHT_LOCAL mode with ChromaDB for offline semantic search over project context
- GITHUB_TOKEN support for higher GitHub API rate limits during lookups
- Configurable LOG_LEVEL for debugging agent-driven sessions
- Server schema version 0.3.1
- stdio transport via npm package midnight-nextjs-mcp
- Three documented environment variables: GITHUB_TOKEN, LOG_LEVEL, MIDNIGHT_LOCAL
What problem does it solve?
Building Midnight dApps on Next.js forces you to merge niche chain SDK knowledge with React app structure while your agent lacks a single integrated tool surface.
Who is it for?
Solo or indie builders already committed to Midnight and Next.js who want agent-assisted contract and dApp integration in the same repo.
Skip if: Teams on non-Midnight chains, backend-only APIs with no Next.js surface, or builders who need managed hosting instead of dev-time MCP tooling.
What do I get? / Deliverables
After registering the server, your agent can query Midnight–Next.js-oriented context and workflows from one stdio MCP endpoint during integration work.
- Registered stdio MCP server for Midnight + Next.js workflows
- Agent-accessible blockchain and frontend integration context
- Optional local semantic search when MIDNIGHT_LOCAL is enabled
Recommended MCP Servers
Journey fit
Blockchain plus frontend app work sits in the build phase when you are implementing product integrations rather than validating ideas or shipping checks. Midnight and Next.js together are cross-stack integrations—wallet flows, SDK calls, and app wiring—not standalone docs or PM artifacts.
How it compares
Chain-specific Next.js integration MCP, not a general-purpose GitHub or browser automation server.
Common Questions / FAQ
Who is Midnight + Next.Js MCP for?
It is for developers building Midnight blockchain dApps with Next.js who use Claude Code, Cursor, or other MCP-capable agents during the build phase.
When should I use Midnight + Next.Js MCP?
Use it while wiring Midnight SDKs, wallet flows, and Next.js pages—especially when you want offline semantic search via MIDNIGHT_LOCAL during deep integration sessions.
How do I add Midnight + Next.Js MCP to my agent?
Add a stdio MCP entry that runs npx on the midnight-nextjs-mcp npm package with Node --experimental-vm-modules, and set GITHUB_TOKEN or LOG_LEVEL if needed.