Your agent can't connect
MCP server status and the 1423 port, what happens after a token is regenerated, same-machine requirements, and re-copying the setup prompt.
Updated
The MCP server runs inside the GeckoGrid app, on a loopback address only. When an agent cannot connect, one of these four causes is nearly always the reason.
The MCP server is not running
Open the AI & MCP page. The status pill shows the real server state, not a guess, and a re-check button refreshes it along with the setup prompt and client configs.
The server listens at http://127.0.0.1:1423/mcp by default. If port 1423 is already occupied, GeckoGrid walks to the next free port automatically, up to nine ports higher, and the setup prompt and config snippets always embed the actual port in use. So a port collision usually needs no fix at all: re-copy the setup prompt or config so the agent targets the right port.
If the status shows the server stopped because every candidate port was busy, close the app holding the ports, or restart GeckoGrid, then re-check the status.
The token was regenerated
The bearer token authenticates every agent request. Regenerating or rotating it invalidates any client still using the old token, so an agent that connected yesterday starts failing today.
On the AI & MCP page, copy the setup prompt again with the current token and paste it into the agent as before. After writing MCP config by hand instead, restart the agent session so the new config loads.
The agent runs on a different machine
The MCP endpoint is loopback-only: 127.0.0.1 from the agent’s point of view must be the machine GeckoGrid runs on. An agent on another computer, in a container, or in a cloud session cannot reach it, by design. Run the agent on the same machine as GeckoGrid.
Config was written but the agent ignores it
MCP connections take effect only after the session restarts. Once the config file is written, tell the agent to restart the session, or restart the app hosting it, before judging the connection broken.
Still stuck? The Logs page, filtered to the System category, records MCP startup problems, including which port was bound and why a bind failed. The full connection walkthrough is on the connecting an agent page.
Was this helpful?