If the agent won't connect
Troubleshooting MCP in Multogram: the agent doesn't see the tools, "Multogram is not running", versions don't match, no connection to the server, no device slot, AI session limit, refusals and errors — what each message means and what to do.
The first thing to do with any problem is to ask the agent to call get_access_status. This
tool is always there, even without the application: it reports whether Multogram is running, whether you are signed in, whether
there is a connection to the server, what the plan unlocks, which agent sessions are running and, in one sentence, what to do.
The agent doesn't see Multogram's tools
Neither get_access_status nor any other tool is there — this means the client didn't start the MCP server.
- Check the path to
mcp.exein the client's settings: the file is in place and the path is written in full. In JSON use forward slashes (C:/Program Files/…) or double the backslashes (C:\\Program Files\\…). - Restart the client or reconnect the server — most clients read the MCP settings at startup.
- Look at the MCP log in the client: it shows why the server didn't start.
- If
mcp.exedisappeared from the folder right after unpacking, your antivirus deleted it. Add the folder to the exclusions and unpack the archive again.
What the agent reports
| Message | What it means | What to do |
|---|---|---|
| Multogram is not running | The application isn't open under this Windows user account | Start Multogram and sign in. The tools appear by themselves within a few seconds |
| The Multogram window hasn't opened MCP yet | The main window is still loading | Wait a few seconds. If it happens again, restart Multogram, and if that doesn't help, update it — see Installation |
| Multogram is starting or closing | The application isn't ready to accept a connection yet | Wait a few seconds and try again |
| Multogram rejected the connection | Multogram accepts only the MCP server released with it, and this mcp.exe is a different build or newer than the application | Use mcp.exe from the folder of the installed Multogram, or update Multogram |
| Versions don't match | The server and the application are from different releases | Update Multogram and take mcp.exe from its folder, or download a fresh archive |
| No access | You aren't signed in to your Multogram account | Sign in to the account in the application |
| The computer isn't linked to the account | The computer has no device slot | Free a slot in your account on the website — see Devices |
| No connection to the Multogram server | No internet or the server is unreachable; the agent names the reason | Check the connection. The agent can still read tasks, accounts and proxies |
| Multogram server error | The server answered with an error | Try again later. If it happens again, the agent will prepare a support ticket |
Refusals during work
| Code | What it means | What to do |
|---|---|---|
SCOPE_DENIED | The action isn't part of your plan | Mode settings and tasks are on Pro and Max, mass actions on Max — see What the agent can do |
SETTINGS_INCOMPLETE | A required field of the mode's settings is empty | The agent names the fields; fill in the secret ones (keys, passwords) yourself, it fills the rest |
ACCOUNTS_MISSING | The task has no accounts to work from | Add accounts, or tell the agent which ones to run from |
CONFLICT | Something else is in the way: the task is still running, or a mass action runs on the accounts | Wait for it to finish, or stop the task |
BATCH_TOO_LARGE | More in one call than the plan allows (Free 100, Pro 250, Max 500) | The agent splits the work into several calls by itself |
TIMEOUT | The action did not answer in time and may have happened | The agent repeats the call with the same request id — Multogram returns the first one's result instead of doing it twice |
NOT_ENTITLED | The mode isn't unlocked for your account | The agent names the plan or purchase that would unlock it — see Plans |
SESSION_LIMIT | All places for running sessions are taken | Answer in the AI session limit window in Multogram — see Limits |
RATE_LIMITED, BUSY | The agent makes requests too often | The agent waits and continues by itself |
CONFIRMATION_DENIED | You denied the action in the confirmation window | The agent won't repeat it and asks what to do differently |
CONFIRMATION_TIMEOUT | The confirmation window closed without an answer | Ask the agent to repeat and answer in the Multogram window |
CLIENT_UNAVAILABLE | The Multogram window is reloading or closed | Wait a few seconds |
APP_ERROR | A failure in Multogram itself | The agent doesn't repeat such a call. Send a ticket with the incident number (MGM-…) — the agent prepares its text |
Common questions
Why did the tools disappear in the middle of work?
You signed out, closed Multogram, or the application restarted. Start it and sign in — the tools come back by themselves, with no need to reconnect the client.
The agent says Multogram isn't running, although the window is open
Two common reasons:
- Different Windows user accounts. The AI client and Multogram must run under the same user.
- An old Multogram version with a downloaded server. A server from an archive that is newer than the application doesn't find MCP of its own version in it. Update Multogram to the latest version.
Can I run mcp.exe manually to check it?
You can, but there is no point: the server waits for commands from the AI client and shows nothing by itself. Check
the connection from the client with get_access_status.
Updated
What the agent can do
What an AI agent can do in Multogram over MCP: adding and checking accounts, proxies, templates, mode settings, tasks and modules, logs, the Modules Constructor. What the Free, Pro and Max plans unlock, action confirmations and limits.
Plans
The Multogram Free, Pro and Max plans and buying individual modes for good: which modes each plan includes, how many devices, billing periods, the Pro trial and how to choose the best option.