Connect Gemini

Add Remote.It as a remote MCP server in Gemini CLI over Streamable HTTP with OAuth sign-in, by editing one config file.

Gemini CLI supports remote MCP servers over Streamable HTTP with OAuth 2.0, so the Remote.It MCP server can be added by editing one config file.

The MCP server URL is:

https://cloud.remote.it/mcp

Before you start

• A Remote.It account — sign up free.

• Gemini CLI installed and signed in.

1

Add the server

Edit ~/.gemini/settings.json and add a remoteit entry under the top-level mcpServers key:

{
  "mcpServers": {
    "remoteit": {
      "httpUrl": "https://cloud.remote.it/mcp",
      "oauth": {
        "enabled": true
      }
    }
  }
}

Gemini CLI discovers the OAuth configuration from the server automatically, so no client ID, authorization URL, or scopes are needed here.

Match the path exactly — /mcp, with no trailing slash. A URL that would normally redirect can break the OAuth flow.

You can also add it from the command line instead of editing the file:

gemini mcp add --transport http remoteit https://cloud.remote.it/mcp

Restart Gemini CLI after changing settings.json — configuration is read at startup, not mid-session.

2

Sign in to Remote.It

Start Gemini CLI and run:

/mcp auth remoteit

This opens your browser. 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 Gemini.

3

Check the connection

/mcp

This lists connected servers and the tools they expose. Compare the list against the Tool Reference. If it's empty, see Troubleshooting.

4

Test it

Ask something that can only be answered from your account:

• "Which of my Remote.It devices are offline?"

• "List the services on my jump box."

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

Start with a read-only question. If the device names match your actual account, the connector is working.

Remote.It gates destructive operations — deleting devices, running scripts — behind an explicit confirmation step.

Optional — Limit the tools

If you only want a subset of the Remote.It tools available, use includeTools or excludeTools. excludeTools wins when a tool appears in both.

{
  "mcpServers": {
    "remoteit": {
      "httpUrl": "https://cloud.remote.it/mcp",
      "oauth": { "enabled": true },
      "excludeTools": ["delete_device"],
      "timeout": 30000
    }
  }
}

This is a useful belt-and-braces measure alongside the scopes you grant at consent, but it is a client-side filter — the authoritative control is your Remote.It account permissions.

Troubleshooting

Symptom	Cause and fix
Server doesn't appear after editing settings.json	Restart Gemini CLI. Configuration is read at startup.
/mcp shows the server but no tools	Check includeTools isn't filtering them out, and confirm the OAuth flow completed with /mcp auth remoteit.
OAuth flow fails or loops	Check the URL is exactly https://cloud.remote.it/mcp with no trailing slash. Complete the browser sign-in in the same profile you're working in.
Server times out on connect	Raise the timeout: "timeout": 120000 in the server's config block.
Tools appear but calls fail with a permissions error	Your Remote.It account or the scopes granted at consent don't cover that operation. See Permissions & Safety, or re-run /mcp auth remoteit to redo consent.

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

• Connect ChatGPT — add the connector to ChatGPT using Developer mode

• Connect Grok — add the connector in the Grok web app, for a team, or via the xAI API