Fix the usual connection problems first.

Pairing code does not work

Pairing codes are 6 digits, valid for five minutes, and single-use. If a code has expired or was already submitted, create a new one in NexusDock and enter the new code in AgentDock.

The device never appears in NexusDock

1. Confirm AgentDock is installed and running on the intended computer.
2. If AgentDock asks for a NexusDock service address, use https://mcp.nexusdock.co/.
3. Create a fresh pairing code and complete pairing again.
4. Return to Devices and refresh the page. A successful connection should show the device as Online.

The device is shown as offline

An offline device usually means AgentDock is stopped, the computer is asleep, or the network connection to NexusDock has been interrupted. Open AgentDock on that device, confirm it is running, then wait for the Devices page to return to Online.

AI is connected but cannot see a new tool

AI clients often cache MCP tool definitions. Refresh or reconnect the NexusDock MCP connection, then start a new conversation. Do this before assuming the NexusDock or AgentDock update failed.

Authorization failed or was cancelled

Return to the AI client and start the connection again. When the NexusDock authorization page opens, make sure you are signed in to the intended account and approve the client. If the client was previously authorized, you can revoke it in NexusDock settings and connect again.

MCP access token stopped working

Resetting the MCP access token immediately invalidates the old token. Update every client that used the old token with the newly generated value. NexusDock only shows a new token once.

Still stuck?

If NexusDock displays a request ID with an error, keep that request ID. It helps diagnose the problem without exposing your credentials.