AI access (MCP)

CubeMind speaks MCP, the protocol AI assistants use to work with other services. Connect your AI once with an access key, then ask it in plain words: "set up three clients on my server on my dedicated IP, with a flow that eats when hungry and logs out at 8". It does the work in your account.

Your AI runs on its own subscription, so CubeMind charges nothing for the thinking. Everything it does goes through the same rules as the dashboard: your plan's client slots, your limits, and the access people shared with you.

Create an access key

Account settings → AI access → Create an access key. AI access comes with a plan; on a free account the section is not shown.

1. Give it a name, for example the computer or AI it is for.
2. Choose what it may do:
   • Read only looks at everything and changes nothing.
   • Manage everything creates and controls clients, logins, dedicated IPs and flows. It cannot spend credits or receive passwords.
   • Custom lets you pick each permission (see the table below). With Spend credits on, you also set the key's Daily spend cap.
3. Optionally set an expiry.

The key is shown once. Copy it or set up your AI straight away; if you lose it, revoke it and create a new one. You can hold up to 10 active keys.

Connect your AI

After you create a key, pick your AI and copy the command. It already contains your key.

Claude Code

claude mcp add --transport http --scope user cubemind https://api.cubemind.net/mcp --header "Authorization: Bearer cmk_…"

Type /mcp in Claude Code to check that CubeMind is connected.

Codex

Set the key as an environment variable, then add the server:

export CUBEMIND_API_KEY="cmk_…"
codex mcp add cubemind --url https://api.cubemind.net/mcp --bearer-token-env-var CUBEMIND_API_KEY

On Windows PowerShell set the key with $env:CUBEMIND_API_KEY="cmk_…". Put it in your shell profile so it is there every time Codex starts.

Gemini CLI

gemini mcp add --transport http --scope user cubemind https://api.cubemind.net/mcp --header "Authorization: Bearer cmk_…"

VS Code, Cursor and others

The AI access page also has a command for VS Code, an Add to Cursor button, and a JSON block for anything else that reads an MCP settings file, such as Claude Desktop.

Let your AI install it

Not keen on terminals? The AI access page has a ready-made prompt. Paste it into Claude Code or Codex and it runs the right command itself, then checks the connection.

The prompt contains your key, so it stays in that chat's history. If the history is shared with anyone, revoke the key and create a new one.

What a key can do

Permission	What it allows
Read	See clients, live state, the console, logins, dedicated IPs, flows and the flow library.
Control	Start, stop and restart clients, send chat and commands, run flow triggers.
Clients	Create, change and delete clients and set their variables.
Logins	Add and delete game logins. Premium logins still need you to complete the premium sign-in yourself.
Dedicated IPs	Add and delete dedicated IPs.
Flows	Write, save, attach, switch on and delete flows; import free library flows.
Spend credits	Buy library flows and rent dedicated IPs, up to the key's daily cap.
Passwords in chat	Pass dedicated IP passwords and secret variables through the chat.

A key never reaches admin pages, billing, sharing or your account settings, whatever it is allowed to do.

Flows written by your AI

Your AI reads the flow reference, checks its flow, and simulates it the same way Try it does before saving. A flow it saves is always switched off, with a link to open it in the editor. It is switched on only when you say so.

Confirmations and the daily spend cap

Deleting a client, login, dedicated IP or flow, and anything that costs credits, is a two-step action. The tool first returns a summary of what it will do and what it costs, and your AI is told to show it to you and go ahead only when you agree. CubeMind cannot see your chat, so that step depends on your AI following its instructions.

The hard limit is the daily spend cap on every key with the Spend credits permission: purchases past it are refused until the next day, whatever the AI does. If the price changes between the summary and the purchase, the purchase is refused too. Leave Spend credits off unless you need it.

Passwords stay out of chat

Unless a key has the Passwords in chat permission, your AI never asks you to type a password into the chat. When a dedicated IP or a client needs one, it gives you a link to the dashboard where you type it yourself. Stored passwords are never sent to your AI.

Text from the game (chat, server messages) is passed to your AI marked as untrusted, and your AI is told never to follow instructions found in it. That lowers the risk of a player talking it into something, but it cannot rule it out, which is another reason to keep risky permissions off.

Revoking a key

AI access → Revoke next to the key. Any AI using it loses access straight away. The page also lists your AI's recent changes, so you can see what each key did.