The normal connection flow
Open NexusDock and check Devices. Connecting an AI client can succeed without an online device, but there will be nothing useful to operate until a device is available.
Use the Copy MCP endpoint action in NexusDock. The production endpoint is https://mcp.nexusdock.co/mcp.
Paste the NexusDock MCP endpoint into the client's MCP, tools, connectors or integrations area. The exact menu name varies by client.
If the client supports OAuth, a browser opens the NexusDock authorization page; sign in and approve the client.
Some AI clients cache tool definitions. After a new device, tool or NexusDock update, refresh the MCP connection and start a new conversation if the tool list looks stale.
ChatGPT, Claude and Cursor
ChatGPT
Add NexusDock from the MCP or connector area available in your ChatGPT environment. Use the NexusDock endpoint and complete browser authorization when prompted.
Claude
Add NexusDock as a remote MCP connection in Claude's integrations or connector settings, then authorize the NexusDock account in the browser.
Cursor
Open Cursor's MCP or tools settings, add a remote HTTP MCP server, paste the NexusDock endpoint, then follow the authorization flow.
Other clients
Any client that supports Remote MCP over Streamable HTTP can use the same NexusDock endpoint. Prefer OAuth when the client offers it.
When OAuth is not available
NexusDock also provides an MCP access token for clients that require manual credentials. Create or reset it in Account & settings, copy it immediately, and store it like a password. The token is shown only once.
Enter credentials only in the AI client's protected connection settings. Reset the token if you think it was exposed.
Connection works, but tools look wrong?
Refresh the NexusDock MCP connection and start a new conversation first. Tool schemas can be cached by the client even after NexusDock or AgentDock has already updated.