Skip to content

MCP: AI assistants

Connect an AI assistant through MCP to ask about your fleet and perform allowed actions. Actions that change settings require explicit permission in Flotera.

  1. Open MCP in the panel and enable access.
  2. Choose the tools the assistant can use and the servers it can access. Start with reading and a limited set of servers.
  3. Follow the connection instructions for your client. Use OAuth when supported, or the token method shown in the panel.

An OAuth connection appears in the client list and can be disconnected individually. Clients using a token do not appear in that list. To reconnect a client you disconnected, remove the connector in the AI app and add it again.

With read access, the assistant can review server health, rentals, market prices, and pricing rules, depending on the tools you enable. The assistant sees each command’s state and a short summary of its result. Logs from your machines stay in the panel.

For changes, enable Write mode and each required tool:

Tool Action
server_run_self_test runs a quick server self-test without load testing
server_set_power_limit sets the GPU power limit
listing_set_price changes the price of a published listing; it never publishes one
strategy_update changes a pricing rule

Full qualification is available in the panel. Asking for the same self-test again within 10 minutes returns the running or just-finished test instead of starting another. MCP does not offer reboot, rental termination, marketplace switching, or wallet operations.

The assistant must respect the server’s supported settings and rental state. For example, it cannot raise a price during a rental. A price change is limited to 15% per call, and the power limit cannot exceed 600 W or the hardware’s supported range. A new power limit also applies during a rental. Several price changes can add up to more than 15%.

The assistant changes prices only of published listings. A listing you hid or withdrew, or one Flotera paused while another marketplace rents the machine, stays as it is — publishing is done in the panel. The 15% limit is counted from the price the marketplace shows right before the change; if that price cannot be read, the change is refused. The power limit must also be at least 50 W. If the marketplace does not confirm a price change, you get a notification that the change may have happened: check the listing before changing it again.

If an action is unavailable or still pending, read the explanation before asking the assistant to repeat it. A tool marked closed by policy cannot run under the account’s current permissions.

The assistant can change listing prices up to 20 times per hour and 10 times per day; the day runs in UTC. Every attempt counts, including one refused by the 15% limit or by the rental state. When a limit is used up, the assistant is told how long until it renews.

Owners and administrators manage MCP settings. Review allowed tools, server scope, and the action log periodically.

Disabling MCP ends access for all connected clients. After re-enabling it, reconnect OAuth clients and replace the token in clients that use one. Write tools must be enabled again; the selected server scope is kept.

You can disable MCP while your account is frozen. Restoring or changing access requires unfreezing the account. Some read tools remain available during a freeze, but their data may be outdated.