Midnight + Next.js MCP

io.github.FractionEstatePublished by GitHub account FractionEstatev0.3.1Updated Oct 25, 2026

Unified MCP server for Midnight blockchain development and Next.js dApps.

VerifiedSTDIODesktop onlyBrowser AutomationDeveloper Tools

Overview

AI-generated overview

Local MCP server that gives an AI assistant Midnight blockchain contract, wallet and network tools alongside Next.js DevTools for building dApps.

What you can do
Initialize a Midnight development context, scaffold dApp projects, compile Compact contracts to TypeScript and ZK artifacts, run static analysis, deploy contracts and execute circuit calls on them. Create wallets, read wallet state and balances, and transfer tDUST tokens. Check network health across Indexer, Proof Server and Node, query blocks and transactions, and check Midnight package versions. Search, fetch, sync and list Midnight documentation. Work with Next.js: initialize a dev context, search Next.js docs, discover running dev servers, run runtime diagnostics, evaluate pages with Playwright, and follow Next.js 16 and Cache Components upgrade guides.
When to use it
Useful when building decentralized applications on the Midnight Network with a Next.js frontend and you want the assistant to compile, analyze, deploy and call contracts, manage test wallets, inspect chain state and consult Midnight and Next.js documentation from one server.
Requirements
Runs locally over stdio, typically via npx with Node.js, or as a global npm install or Docker container. Optional GITHUB_TOKEN raises API rate limits; LOG_LEVEL sets logging verbosity; MIDNIGHT_LOCAL enables local mode with ChromaDB for offline semantic search. Network endpoints default to Midnight testnet and can be overridden by environment variables. Network access is needed for chain queries and documentation sync.
Before you install
The server can deploy contracts, execute circuit calls and transfer tDUST tokens, which move funds and change on-chain state. Wallet creation generates a seed phrase, so treat any seed or key material as sensitive. GITHUB_TOKEN is a secret and should be scoped narrowly. Contract and documentation operations contact Midnight network services and GitHub.

Installation

In SourceWeft

  1. Open Midnight + Next.js MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Midnight + Next.js Development MCP Server

A Model Context Protocol (MCP) server combining Midnight Network blockchain development tools with Next.js DevTools for building decentralized applications.

Compatible with all MCP-enabled AI assistants: Claude, GitHub Copilot, Cursor, Windsurf, Codeium, Continue.dev, Zed, Sourcegraph Cody, and more.

🤖 Supported AI Assistants

This MCP server works with any AI assistant that supports the Model Context Protocol:

AI AssistantPlatformConfiguration
ClaudeDesktop App, VS CodeNative MCP support
GitHub CopilotVS Code, JetBrainsMCP extension
CursorIDEBuilt-in MCP support
WindsurfIDEBuilt-in MCP support
CodeiumVS Code, JetBrainsMCP integration
Continue.devVS Code, JetBrainsMCP config file
ZedIDEMCP support
Sourcegraph CodyVS CodeMCP extension

🌙 Features

Midnight Network Tools

Contract Development
  • midnight_init - Initialize development context
  • midnight_compile_contract - Compile Compact contracts to TypeScript/ZK artifacts
  • midnight_analyze_contract - Static analysis for contracts
  • midnight_deploy_contract - Deploy contracts to the network
  • midnight_call_contract - Execute circuit calls on deployed contracts
  • midnight_scaffold_project - Create new dApp projects from templates
Wallet & Tokens
  • midnight_create_wallet - Generate new wallet with seed phrase
  • midnight_wallet_state - Get detailed wallet state and balances
  • midnight_transfer_tokens - Transfer tDUST tokens
  • midnight_get_balance - Query token balances
Network & Queries
  • midnight_network_status - Check network health (Indexer, Proof Server, Node)
  • midnight_get_block - Query blockchain blocks
  • midnight_get_transaction - Query transaction details
  • midnight_check_versions - Check for Midnight package updates
Documentation
  • midnight_search_docs - Search Midnight documentation
  • midnight-fetch-docs - Fetch specific documentation pages
  • midnight-sync-docs - Sync documentation from official repo
  • midnight-docs-status - Check documentation sync status
  • midnight-list-docs - List available documentation sources

Next.js DevTools

  • init - Initialize Next.js development context
  • nextjs_docs - Search Next.js documentation
  • nextjs_index - Discover running dev servers
  • nextjs_call - Execute runtime diagnostic tools
  • browser_eval - Browser automation with Playwright
  • upgrade_nextjs_16 - Next.js 16 upgrade guide
  • enable_cache_components - Cache Components migration

📦 Installation

bash
# Clone the repositorygit clone https://github.com/your-username/midnight-nextjs-mcp.gitcd midnight-nextjs-mcp
# Install dependenciespnpm install
# Buildpnpm build

🚀 Usage

Quick Start with npx

The easiest way to use this MCP server is via npx — no installation required:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}

Configuration Examples

The MCP configuration format is standardized across most AI assistants. Below are platform-specific examples:

Universal MCP Configuration

Most MCP clients use this standard JSON format. Add to your client's MCP configuration file:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}
VS Code (GitHub Copilot / Claude Extension)

Add to your VS Code settings.json or workspace .vscode/mcp.json:

json
{  "mcp.servers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}

Or for Claude extension specifically:

json
{  "claude.mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}
Claude Desktop (macOS)

Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}
Claude Desktop (Windows)

Edit %APPDATA%\Claude\claude_desktop_config.json:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}
Claude Desktop (Linux)

Edit ~/.config/Claude/claude_desktop_config.json:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}
Cursor IDE

Add to your Cursor MCP configuration (.cursor/mcp.json in your project or global settings):

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}
Windsurf / Codeium

Add to your Windsurf MCP settings:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}
Continue.dev (VS Code / JetBrains)

Add to ~/.continue/config.json or your project's .continue/config.json:

json
{  "experimental": {    "modelContextProtocolServers": [      {        "name": "midnight-nextjs-mcp",        "transport": {          "type": "stdio",          "command": "npx",          "args": ["-y", "midnight-nextjs-mcp@latest"]        }      }    ]  }}
Zed Editor

Add to your Zed settings (~/.config/zed/settings.json on Linux, ~/Library/Application Support/Zed/settings.json on macOS):

json
{  "context_servers": {    "midnight-nextjs-mcp": {      "command": {        "path": "npx",        "args": ["-y", "midnight-nextjs-mcp@latest"]      }    }  }}
Sourcegraph Cody

Add to your Cody MCP configuration:

json
{  "cody.experimental.mcp.servers": {    "midnight-nextjs-mcp": {      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}
JetBrains IDEs (IntelliJ, WebStorm, etc.)

For AI assistants in JetBrains IDEs that support MCP, add to your MCP configuration:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"]    }  }}
Using Global Installation

If you prefer a global install instead of npx:

bash
npm install -g midnight-nextjs-mcp

Then configure:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "midnight-nextjs-mcp"    }  }}
Local Development / From Source
json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "node",      "args": ["/path/to/midnight-nextjs-mcp/dist/index.js"]    }  }}
Docker

Run the MCP server in a Docker container:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "docker",      "args": ["run", "-i", "--rm", "fractionestate/midnight-nextjs-mcp:latest"]    }  }}

CLI Flags

bash
# Enable both tool categories (default)npx midnight-nextjs-mcp@latest
# Disable Midnight tools (Next.js only)npx midnight-nextjs-mcp@latest --no-midnight
# Disable Next.js tools (Midnight only)npx midnight-nextjs-mcp@latest --no-nextjs
# Check package versions on startupnpx midnight-nextjs-mcp@latest --check-versions
# Set version polling interval (default 24 hours)npx midnight-nextjs-mcp@latest --poll-interval=12

🏗️ Project Structure

midnight-nextjs-mcp/├── src/│   ├── index.ts                    # Server entry point│   ├── tools/│   │   ├── index.ts                # Unified tool registry│   │   ├── midnight/               # Midnight Network tools│   │   │   ├── init.ts│   │   │   ├── network-status.ts│   │   │   ├── get-balance.ts│   │   │   ├── get-block.ts│   │   │   ├── get-transaction.ts│   │   │   ├── search-docs.ts│   │   │   ├── scaffold-project.ts│   │   │   ├── compile-contract.ts│   │   │   └── analyze-contract.ts│   │   └── nextjs/                 # Next.js DevTools│   │       ├── init.ts│   │       ├── nextjs-docs.ts│   │       ├── nextjs_index.ts│   │       ├── nextjs_call.ts│   │       ├── browser-eval.ts│   │       ├── upgrade-nextjs-16.ts│   │       └── enable-cache-components.ts│   ├── providers/                  # Midnight API providers│   │   ├── index.ts│   │   ├── indexer.ts              # GraphQL indexer client│   │   ├── proof-server.ts         # Proof generation client│   │   └── node.ts                 # Node RPC client│   ├── resources/                  # MCP resources│   │   ├── (midnight-compact)/     # Compact language docs│   │   ├── (midnight-sdk)/         # SDK documentation│   │   ├── (cache-components)/     # Next.js cache docs│   │   └── ...│   ├── prompts/                    # MCP prompts│   │   ├── create-midnight-contract.ts│   │   ├── upgrade-nextjs-16.ts│   │   └── enable-cache-components.ts│   └── types/                      # TypeScript definitions│       ├── midnight.ts│       └── mcp.ts├── package.json└── README.md

🔧 Configuration

Environment Variables

You can pass environment variables to the MCP server in your configuration:

json
{  "mcpServers": {    "midnight-nextjs-mcp": {      "type": "stdio",      "command": "npx",      "args": ["-y", "midnight-nextjs-mcp@latest"],      "env": {        "MIDNIGHT_NETWORK": "testnet",        "MIDNIGHT_INDEXER_URL": "https://indexer.testnet.midnight.network/graphql"      }    }  }}
Available Environment Variables
bash
# Midnight Network (optional, defaults to testnet)MIDNIGHT_NETWORK=testnetMIDNIGHT_INDEXER_URL=https://indexer.testnet.midnight.network/graphqlMIDNIGHT_PROOF_SERVER_URL=https://proof-server.testnet.midnight.networkMIDNIGHT_NODE_URL=https://rpc.testnet.midnight.network

Network Configurations

NetworkIndexerProof Server
Testnetindexer.testnet.midnight.networkproof-server.testnet.midnight.network
Devnetlocalhost:8080localhost:6300

📚 Resources

The server exposes documentation resources:

Midnight Resources

  • midnight://compact/overview - Compact language introduction
  • midnight://compact/reference - Complete syntax reference
  • midnight://sdk/overview - Midnight.js SDK guide

Next.js Resources

  • nextjs-docs://llms-index - Documentation index
  • cache-components://overview - Cache Components guide

🧪 Development

bash
# Watch modepnpm dev
# Type checkpnpm typecheck
# Run testspnpm test
# Buildpnpm build

📖 Documentation

Client-Specific MCP Documentation

🤝 Contributing

Contributions welcome! Please read the contributing guidelines first.

📄 License

MIT License - see LICENSE for details.

Built with ❤️ for the Midnight and Next.js communities.

Source: README.md at commit 4a88d65

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.3.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.