
Prover MCP
from d3lta02
Integrates with the Succinct Prover Network to monitor, calibrate, and optimize prover operations.
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.
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)
- Visit: https://staking.sepolia.succinct.xyz/prover
- Connect wallet & create prover
- Save prover address (different from wallet address!)
-
๐ฐ Stake PROVE Tokens (Manual)
- Visit: https://staking.sepolia.succinct.xyz
- Stake minimum 1000 PROVE tokens
-
โ๏ธ Calibrate Hardware (AI Assisted)
- Command: "Calibrate my prover hardware"
-
๐ Run Prover (AI Assisted)
- Command: "Run Succinct 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.
Security
๐ 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 monitoringResources
- ๐ Official Succinct Documentation
- ๐ Succinct Prover Network
- ๐ฐ PROVE Token Faucet
- ๐๏ธ Prover Staking Interface
git clone https://github.com/d3lta02/prover-mcp.git
cd prover-mcp
npm install
npm run buildBefore it works, you'll need: PROVER_ADDRESSPRIVATE_KEY
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
๐ 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.
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
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 suiteLicensed under MITโ you can use, modify, and redistribute it under that license's terms.
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.