Connect ChatGPT

Add Remote.It as a custom connector in ChatGPT so it can inventory and manage your devices in conversation, using OAuth sign-in with no API keys.

ChatGPT can use the Remote.It MCP server as a custom connector. Once added, you can ask ChatGPT about your devices, open connections, and run the same operations available in the web portal.

The MCP server URL is:

https://cloud.remote.it/mcp

Before you start

• A Remote.It account — sign up free.

• A ChatGPT plan that includes Developer mode. Custom MCP connectors are not available on the Free plan. On Business, Enterprise, and Edu workspaces a workspace admin must allow custom connectors before the option appears for you.

• ChatGPT on the web. Developer mode is configured in the web app. Once a connector is added there, it may also be usable in ChatGPT's other apps.

OpenAI has moved this feature and renamed parts of it more than once ("connectors" → "apps" → "plugins"). If a menu below isn't where we say it is, check the other locations listed in Troubleshooting.

1

Turn on Developer mode

Open ChatGPT on the web and go to Settings → Security and login, then turn on Developer mode.

If you don't see the toggle, see Troubleshooting.

2

Add the Remote.It connector

Go to the ChatGPT Plugins page and select the + button, then fill in the connector details:

Field	Value
Name	Remote.It
Description	Manage Remote.It devices, connections, services, and networks.
MCP server URL	https://cloud.remote.it/mcp
Authentication	OAuth

The description is not cosmetic — ChatGPT reads it when deciding whether the connector is relevant to your question. Keep it specific about what Remote.It does.

Create the connection. ChatGPT connects to the server and lists the tools it discovered. Compare this list against the Tool Reference — if it's empty or much shorter than expected, the connection didn't complete.

3

Sign in to Remote.It

The first time ChatGPT uses a Remote.It tool, it opens a browser sign-in. Sign in with your normal Remote.It account (social sign-in and 2FA both work), then review the consent screen and choose what to grant. You can restrict the connector to read-only access here — see Permissions & Safety.

You never paste an API key or secret into ChatGPT.

4

Enable the connector in a chat

Adding a connector does not switch it on. It has to be selected per conversation.

Start a new chat, select the + next to the message box (or open the Developer mode tool in the composer), and choose Remote.It.

The connector stays active for the rest of that conversation. New conversations start with it off again.

5

Test it

Ask something that can only be answered from your account:

• "List my Remote.It devices and tell me which are offline."

• "What services are configured on my jump box?"

• "Open an SSH connection to my office Raspberry Pi."

The first is read-only and safe for a first test. If the device names match your actual account, the connector is working.

ChatGPT asks you to confirm before it runs any tool that writes or changes something, and Remote.It adds its own confirmation gate on destructive operations such as deleting devices or running scripts. Expect two prompts on those, not one.

Limits worth knowing

• Remote servers only. ChatGPT cannot reach a server on your laptop or private network. The Remote.It MCP server is hosted, so this is not a problem here.

• Deep research mode is different. In deep research, ChatGPT only uses search and fetch-style tools, not the full Remote.It tool set. Use a normal chat for device operations.

• Per-chat activation. See step 4 above. This is the single most common reason people think the connector is broken.

• Custom connectors are not verified by OpenAI. ChatGPT will warn you about this when you add one. It applies to every custom connector, Remote.It included.

Troubleshooting

Symptom	Cause and fix
No Developer mode toggle in Settings → Security and login	Check Settings → Connectors → Advanced settings and Settings → Apps → Advanced settings — OpenAI has used all three locations. If it's absent everywhere, you're on a plan without it, or a workspace admin has disabled custom MCP connectors (Workspace Settings → Permissions & Roles → Connected Data).
Connector saves but no tools are listed	The URL is wrong or missing the /mcp path. It must be exactly https://cloud.remote.it/mcp.
Connector added but ChatGPT says it has no Remote.It tools	The connector isn't enabled in this conversation. See step 4 above.
Sign-in loops or never completes	Complete the browser sign-in in the same browser profile you're using for ChatGPT, then retry the prompt.
ChatGPT sits silently after proposing a tool call	It's waiting on your confirmation. Approve or reject the call in the chat.
Tools appear but calls fail with a permissions error	Your Remote.It account or the scopes you granted at consent don't cover that operation. Review Permissions & Safety, or disconnect and reconnect to re-run the consent screen.

Next steps

• Tool Reference — every tool the server exposes

• Prompt Library — things to ask, grouped by task

• Permissions & Safety — scopes, consent, and safety gates

• Connect Claude — add the connector to Claude on web, desktop, mobile, or Claude Code