Is there a Foreman MCP server?

You don't need an MCP server to give your agent Foreman. Jentic connects it directly from the API Directory: import it, store your credential once, and your agent calls operations like reading a miner summary or rebooting a miner on demand, without loading another server's tool definitions into its context.

Can I limit what my agent is allowed to do with Foreman?

Yes. Write a rule that allows only the read and monitoring operations under one client id, such as the miner summary and detailed status reads, so the agent can watch the fleet but cannot reboot, overclock, or delete a miner unless you add those actions, and every call it makes is logged. This matches a monitoring bot that reports problems without touching the hardware.

Can I reboot miners remotely with the Foreman API?

Yes. Call the reboot action with a miner id to restart it, and the status operation returns a command id you can poll for the action's result. Other remote actions include changing pools, setting power mode, and overclocking supported firmware.

What are the rate limits for the Foreman API?

The OpenAPI spec does not specify rate limits. Check the Foreman documentation at https://dashboard.foreman.mn for current limits before running bulk actions across a large fleet.

How do I monitor and recover miners with the Foreman API through Jentic?

Search Jentic for 'monitor crypto miners', which returns the miner summary and reboot operations with their input schemas. The agent polls the summary for a client, finds offline miners, and reboots them, with your stored key injected at call time. To run it on your own infrastructure, install Jentic One from its GitHub repo.