Prover MCP
Integrates with Docker to run and manage Succinct Prover Network containers, including hardware calibration, prover operations, and container monitoring.
Enables interaction with the Succinct Prover Network on Ethereum's Sepolia testnet, including prover contract management, PROVE token staking, proof request handling, and earning rewards for generating proofs.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Prover MCP calibrate my prover hardware"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Prover MCP
⚠️ Testnet Only: This MCP is for Sepolia testnet only.
A Model Context Protocol (MCP) server that enables AI assistants to control Succinct Prover Network operations following the official Succinct workflow.
Prerequisites
⚠️ Security Notice: Use only fresh test wallets for Sepolia testnet. Never use mainnet private keys!
Required Software
Node.js 18+ - Download here
Docker Desktop - Download here
⚠️ Must be running before setup
Required Blockchain Assets
Fresh Ethereum Wallet
Create a new wallet (MetaMask, etc.)
Get Sepolia ETH from faucet
Export private key (64 hex characters, no 0x prefix)
PROVE Tokens
Get 1000+ PROVE tokens from official faucet
Minimum 1000 PROVE required for staking
Related MCP server: Avalanche MCP Tools
🚀 Quick Setup
Installation
git clone https://github.com/d3lta02/prover-mcp.git
cd prover-mcp
npm install
npm run buildSetup Options
Option 1: Interactive Setup (Recommended)
npm run init
# Choose: Interactive Setup
# Select: AI client preference
# Optional: Add credentials during setupOption 2: Auto Setup (Fastest)
npm run init
# Choose: Auto Setup
# Automatically configures detected AI clientsCheck Prover MCP & You're Ready
npm start
# Succinct Prover Network MCP Server runningBoth methods create:
📄
.envfile with configuration template🤖 AI client MCP configurations (Claude/Cursor)
📋 Next steps following official Succinct workflow
Configuration Methods
Method 1: MCP Config (Recommended)
Environment variables are set directly in your AI client's MCP configuration:
Claude Desktop: ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor IDE: ~/.cursor/mcp.json
{
"mcpServers": {
"succinct-prover": {
"command": "node",
"args": ["./build/index.js"],
"cwd": "/path/to/your/prover-mcp",
"env": {
"PROVER_ADDRESS": "your_prover_contract_address",
"PRIVATE_KEY": "your_64_character_private_key_no_0x_prefix"
}
}
}
}Method 2: Environment File
Edit the .env file created by setup:
# Edit with your real credentials
PROVER_ADDRESS=0x1234567890123456789012345678901234567890
PRIVATE_KEY=1234567890123456789012345678901234567890123456789012345678901234💡 Pro Tip: MCP config method bypasses tool cache issues and provides better reliability.
Official Succinct Workflow
The setup follows the official 5-step Succinct workflow:
✅ Requirements (Automated by setup)
Fresh Ethereum wallet with Sepolia ETH
1000+ PROVE tokens from faucet
Docker Desktop running
🏗️ Create Prover Contract (Manual)
Connect wallet & create prover
Save prover address (different from wallet address!)
💰 Stake PROVE Tokens (Manual)
Stake minimum 1000 PROVE tokens
⚙️ Calibrate Hardware (AI Assisted)
Command: "Calibrate my prover hardware"
🚀 Run Prover (AI Assisted)
Command: "Run Succinct Prover"
Usage After Setup
Basic Commands
💬 "Run Succinct Prover" - Start the prover and earn PROVE tokens
💬 "Calibrate my prover hardware" - Optimize performance settings
💬 "Show Succinct workflow" - Check setup progress
💬 "Get my prover status" - View current earnings and performance
Advanced Commands
💬 "Get proof requests" - View available proof requests
💬 "Get my account balance" - Check PROVE token balance
💬 "Stop my prover" - Gracefully stop the prover
Manual Terminal Monitoring
For advanced users who want to monitor prover logs directly in terminal:
# Find your container ID
docker ps | grep succinct
# Stream live logs
docker logs -f CONTAINER_ID
# Monitor resource usage
docker stats CONTAINER_ID💡 Note: Replace CONTAINER_ID with your actual container ID. The MCP provides smart log viewing, but terminal monitoring offers real-time streaming for power users.
How It Works
The MCP server provides secure access to Succinct Prover Network operations:
Environment Loading: Credentials loaded from MCP config (priority) or .env file
Docker Integration: Official Succinct Docker images with hardware optimization
AI Commands: Natural language interface to prover operations
Security: Sepolia testnet only, credentials never logged
The MCP configuration ensures environment variables are available to all tools, bypassing cache issues.
Troubleshooting
Common Issues
❌ "Environment validation failed"
Ensure credentials are set in MCP config or .env file
Restart your AI client completely after configuration changes
❌ "Docker not found"
Install and start Docker Desktop
Verify:
docker --version
❌ "Tool cache issues"
Use MCP config method instead of .env file
MCP config bypasses tool cache limitations
❌ "No PROVE tokens"
Get tokens from official faucet
Minimum 1000 PROVE required for staking
Debug Commands
npm run validate # Validate installation
npm run init # Re-run setup process
npm test # Run test suiteSecurity
🔒 CRITICAL SECURITY NOTES
Testnet Only: This MCP only works with Sepolia testnet
Fresh Wallets: Use dedicated test wallets, never mainnet wallets
Private Keys: Never commit credentials to version control
Official Sources: Only use official Succinct URLs and contracts
All credential files are automatically git-ignored for security.
Development
Build
npm run buildTesting
npm test
npm run validateFile Structure
src/
├── index.ts # MCP server entry point
├── main.ts # CLI argument handling
├── cli/init.ts # Interactive setup tool
├── tools/prover/ # Prover network tools
├── tools/network/ # Network status tools
└── tools/monitoring/ # Performance monitoringContributing
Fork the repository
Create feature branch:
git checkout -b feature-nameFollow the official Succinct documentation
Test with Sepolia testnet only
Submit pull request
Resources
License
MIT License - See LICENSE file for details.
⚡ Ready to start earning PROVE tokens? Run npm run init and follow the setup!
💡 Important: The
cwd(current working directory) parameter is automatically set bynpm run initto ensure relative paths work correctly across different installations.
Available Tools
25 toolsauto_stream_prover_logsB
🔴 Continuous auto-streaming prover logs with periodic refresh (no manual commands)
Inputs: lines, containerId, refreshCount.
calibrate_prover_hardwareB
Official Succinct hardware calibration to determine optimal bidding parameters for maximum profitability
Inputs: mode, usdCostPerHour.
create_artifactC
Create and store artifacts on the network
Inputs: artifactType (required), metadata.
create_proverC
(MANUAL STEP) Provides the URL to create your prover contract on-chain.
Inputs: stakerFeeBips.
debug_environmentC
Get detailed environment debugging and auto-restore report
Inputs: random_string (required).
detect_hardwareC
Smart hardware detection with official Succinct requirements analysis and competitive profitability assessment
Inputs: random_string (required).
get_account_balanceB
Get PROVE token balance for an account
Inputs: address.
get_account_infoC
Get detailed account information and statistics
Inputs: address.
get_environment_statusC
Get detailed environment configuration and .env file status
Inputs: random_string (required).
get_filtered_requestsB
Get unassigned proof requests matching criteria
Inputs: version, minDeadline.
get_network_statsC
Get overall network statistics
Inputs: random_string (required).
get_nonceB
Get current account nonce for transaction ordering
Inputs: address.
get_proof_statusB
Get status of a proof request
Inputs: requestId (required).
get_prove_faucetB
Get information about PROVE token faucet for testing
Inputs: random_string (required).
get_prover_metricsC
Get detailed prover performance metrics
Inputs: timeRange, proverAddress.
get_prover_statusA
Get real-time status, performance metrics, and earnings of your running prover
Inputs: containerId.
get_system_healthB
Get MCP system health and status information
Inputs: detailed.
request_proofC
Submit a proof request to the network
Inputs: vkHash (required), stdinUri (required), cycleLimit (required), version, +1 more.
run_proverC
🌟 (v2) Complete automated Succinct Prover setup & execution - The ONE CLICK solution to start earning PROVE tokens! Follows official 5-step workflow.
Inputs: mode, privateKey, autoCalibrate, proverAddress.
show_live_prover_logsA
🔴 Show real-time live logs from your running Succinct Prover with extended history and activity monitoring
Inputs: lines, containerId.
stake_to_proverB
(MANUAL STEP) Provides the URL to stake PROVE tokens to your prover on-chain.
Inputs: amount (required), proverAddress (required).
stop_proverB
Gracefully stop your Succinct Prover with proper cleanup
Inputs: force, containerId.
stream_prover_logs_to_terminalA
🔴 Get the exact docker logs -f terminal command for classic live streaming UX (copy & paste to terminal)
Inputs: lines, containerId.
submit_bidB
Submit a bid for a proof request
Inputs: deadline (required), bidAmount (required), requestId (required).
verify_proofC
Verify a proof using its URI and verification key
Inputs: vkHash (required), proofUri (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 25 tools
Most tools have clearly distinct purposes, but there is some overlap among the three logging tools (auto_stream_prover_logs, show_live_prover_logs, stream_prover_logs_to_terminal) and between debug_environment and get_environment_status, which could cause misselection.
Tool names consistently use snake_case and follow a verb_noun pattern (e.g., get_account_balance, create_prover). However, verbs like 'show' and 'stream' deviate slightly from the dominant 'get' pattern, and some names are lengthy.
25 tools is at the upper bound of typical server scope. While many are justified for comprehensive prover management, the multiple logging tools and some environment utilities could be consolidated, making it slightly heavy.
The tool surface covers the full prover lifecycle: creation, running, monitoring, staking, and proof handling. Minor gaps exist (e.g., no tool to update prover configuration or manage artifacts beyond creation), but overall it is well-rounded.
Related MCP Connectors
Native Solana staking for AI agents. 26 MCP tools, one-shot signing, webhooks.
AI-native programming language and toolchain for accountable, verifiable agent-driven development.
AI Agent Utility Layer for agent safety, web monitoring, crypto research and tool discovery.
MCP server connecting AI agents to non-custodial staking data across 130+ networks.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables secure interactions with cryptocurrency daemon RPC interfaces through AI assistants, supporting transaction management, wallet operations, and daemon monitoring for Bitcoin-derived cryptocurrencies.1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceEnables natural language interaction with the Avalanche blockchain through AI assistants, allowing users to execute Avalanche CLI commands and AvalancheJS API operations without technical knowledge.1-
- AlicenseNot gradedqualityDmaintenanceA powerful toolkit that enables seamless interaction with EVM-compatible networks through natural language processing and AI assistance, allowing users to manage wallets, launch tokens, and interact with blockchain networks.MIT

MIDL MCP Serverofficial
AlicenseAqualityDmaintenanceEnables AI assistants to interact with the MIDL blockchain, supporting smart contract deployment, balance queries, asset bridging, Bitcoin Rune management, and more through natural language.291MIT