Minerstat

@minerstat show me the current hashrate and power consumption across all my mining rigs

Based on your Minerstat account, you have 12 active workers. Total hashrate is 1.45 GH/s across Ethereum mining. Combined power draw is 3,240W. Top performer is rig-05 at 145 MH/s using 285W. Two workers (rig-08, rig-11) show reduced hashrate in the last hour — rig-08 dropped from 120 MH/s to 95 MH/s at 14:22 UTC. All rigs report normal GPU temperatures between 58-64°C.

This example assumes the MCP can read worker status and aggregate metrics. Minerstat's API requires an API key with read access to your mining farm. Real-time data accuracy depends on worker reporting intervals (typically 60-120 seconds). If workers go offline, they may still appear in totals until the next sync.

@minerstat switch rig-03 to the backup mining pool and restart the miner software

Pool switch initiated for rig-03. Changing from primary pool (ethermine.org) to backup pool (flexpool.io) in worker config. Miner restart command sent at 15:47 UTC. Worker rig-03 will reconnect within 30-45 seconds. You'll see a brief hashrate drop during the restart. Monitor the worker dashboard to confirm the new pool connection appears in the next status update.

This example demonstrates remote worker management. The MCP must have write permissions on your Minerstat account. Pool switches and restarts cause 30-60 seconds of downtime per worker. If the backup pool credentials are misconfigured, the worker may fail to connect — always verify pool settings before issuing restart commands at scale.

@minerstat analyze my profitability over the last 7 days and recommend whether I should switch any rigs to mine Ravencoin instead of Ethereum

Your 12-rig farm earned an estimated $47.30 over the past week mining Ethereum (after electricity costs at $0.12/kWh). Average daily profit: $6.76. Ravencoin profitability for your hardware (NVIDIA RTX 3070 cards) is currently $5.20/day at the same power cost — 23% lower than Ethereum. Network difficulty for Ravencoin dropped 8% this week, but coin price fell 12%, offsetting the difficulty advantage. Recommendation: stay on Ethereum unless you expect a Ravencoin price recovery or want to accumulate RVN for long-term holding.

This synthesis example pairs Minerstat's historical earnings data with the AI's ability to compare profitability across coins. Accuracy depends on Minerstat tracking your electricity rate and the MCP accessing current coin prices. Profitability calculations assume your hardware specs are correctly configured in Minerstat. Switching coins mid-week may incur pool payout delays.

When Minerstat fits a small crypto mining operation

A 3-person team running 20-50 mining rigs needs real-time hashrate and profitability data without switching tabs. Minerstat's API key auth means you can pull rig status, wallet balances, and pool stats into a shared Switchy workspace where the ops lead and two techs coordinate downtime and hardware swaps. The win is consolidation: instead of three people checking the Minerstat dashboard separately, one agent query surfaces which rigs dropped offline overnight. The threshold: if you're managing fewer than 10 rigs or only check stats once a week, the MCP is overkill—just bookmark the dashboard. For teams running daily ops calls and troubleshooting hardware in real time, this keeps mining telemetry in the same workspace as your maintenance runbooks and vendor contacts.

When this MCP supports profitability planning

A 2-person crypto advisory shop models mining profitability for clients considering hardware purchases or coin switches. Minerstat's API exposes current coin prices, network difficulty, and hardware benchmarks—data that changes hourly. In Switchy, the advisor and analyst run "what-if" queries during client calls: "If we switch from ETH to RVN on these ASICs, what's the 30-day revenue delta?" The MCP pulls live rates so the model isn't stale by the time the client decides. The boundary: if your clients only want quarterly reports, a manual CSV export works fine. If you're fielding live questions about hardware ROI or coin migration timing, the MCP keeps your models current without opening five browser tabs mid-call.

When Minerstat helps evaluate pool migrations

A solo miner or small collective evaluates whether to migrate rigs from one pool to another based on payout consistency and fee structures. Minerstat tracks per-pool stats across multiple accounts, and the MCP surfaces that data in a Switchy thread where the team compares 7-day payout variance and uptime. The use case is narrow: you need historical pool data for at least two pools and you're making a decision that affects revenue by more than 5%. If you're loyal to one pool or only mine as a hobby, the comparison overhead isn't worth it. For teams that rotate pools quarterly or run split deployments to hedge downtime risk, this MCP turns pool analytics into a shared decision log instead of a spreadsheet one person maintains.