Connect Grok

Add Remote.It as a custom MCP connector in Grok — in the web app, provisioned for a Grok Business team, or attached to xAI API requests.

Grok supports bring-your-own MCP connectors, so the Remote.It MCP server can be added directly in the Grok web app, provisioned for a team, or attached to xAI API requests.

The MCP server URL is:

https://cloud.remote.it/mcp

Before you start

• A Remote.It account — sign up free.

• A Grok account. Custom connectors are added at grok.com/connectors.

• For team-wide setup, a Grok Business team and management permissions in the xAI console.

Option 1 — Add it in the Grok web app

This is the fastest path and the right one for testing.

1

Open the connectors page

Go to grok.com/connectors, select New Connector, then choose Custom.

2

Enter the server URL

https://cloud.remote.it/mcp

3

Sign in to Remote.It

Complete the authentication flow. Grok opens a browser window to sign in to Remote.It — use your normal account, then review the consent screen and choose what to grant. See Permissions & Safety.

You never paste an API key or secret into Grok.

4

Confirm the tools were discovered

Grok discovers the tools the server exposes and makes them available in conversations, alongside its built-in and catalog connectors. Compare the list against the Tool Reference — if it's empty or much shorter than expected, the connection didn't complete.

Test it

Ask Grok something that can only be answered from your account:

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

• "List the services on my jump box."

• "Connect to SSH on my office Raspberry Pi."

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

Unlike some clients, Grok uses connector tools automatically when your question relates to the service — you don't have to enable it per conversation.

Option 2 — Provision it for a team

Team admins can add Remote.It once so it appears in every member's connector list.

1

Open your team in the xAI console

Sign in to console.x.ai and select your team.

2

Add the connector

Go to Grok Business → Connectors, select + Add Connector, then choose Other. Enter:

https://cloud.remote.it/mcp

Adding the connector at the team level only publishes the definition. Each member still connects their own Remote.It account at grok.com/connectors and runs their own sign-in, so every user's Remote.It permissions are enforced individually.

Adding or removing connectors requires team management permissions.

Option 3 — Use it from the xAI API

Grok's Remote MCP Tools let you attach the server to an API request. xAI manages the connection to the MCP server on your behalf. This is supported in the xAI native SDK, the OpenAI-compatible Responses API, and the Speech-to-Speech API.

import os
from openai import OpenAI

client = OpenAI(
    api_key=os.getenv("XAI_API_KEY"),
    base_url="https://api.x.ai/v1",
)

response = client.responses.create(
    model="grok-4.6",
    input=[
        {"role": "user", "content": "Which of my Remote.It devices are offline?"}
    ],
    tools=[
        {
            "type": "mcp",
            "server_url": "https://cloud.remote.it/mcp",
            "server_label": "remoteit",
            "server_description": "Remote.It device inventory, connections, services, and networks.",
        }
    ],
)

print(response)

Notes for the API path:

• Use allowed_tools to restrict the request to the tools you actually need. Every tool definition consumes context, and the Remote.It server exposes a lot of them — see the Tool Reference.

• Give a clear server_label and server_description, especially if you attach more than one MCP server to the same request.

• require_approval and connector_id from the OpenAI Responses API are not currently supported by xAI. Do not rely on client-side approval gates here — build your own confirmation step around anything that writes.

• Authentication over the API is not the browser OAuth flow used in the web app. Confirm the token handling for your account before wiring this into anything that can change device state.

Because Grok invokes connector tools automatically and the API path has no client-side approval gate, treat write operations with more care here than in clients that confirm every call. Remote.It's own confirmation gate on destructive actions such as deleting devices or running scripts still applies.

Troubleshooting

Symptom	Cause and fix
New Connector → Custom isn't available	Check whether your account tier or workspace policy allows custom connectors. On a managed team, an admin may need to add it from the console instead (Option 2).
Connector added but no tools appear	The URL is wrong or missing the /mcp path. It must be exactly https://cloud.remote.it/mcp.
Grok answers from general knowledge instead of your account	Name the service in your prompt — "using Remote.It, list my offline devices" — to push it toward the connector.
Sign-in never completes	Run the sign-in in the same browser profile you're using for Grok, then retry the prompt.
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 disconnect and reconnect to re-run the consent screen.
Team members don't see the connector after an admin added it	They still need to connect their own account at grok.com/connectors. Admin publishing sets up the definition, not the per-user token.

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