# Connect DoorOps to Grok Bot and Grok

Grok Bot and Grok can work with your DoorOps records through a custom MCP connection. Sign in with your DoorOps account, then ask for job information, paperwork reviews or a proposed operational change.

You need MCP access enabled for your DoorOps company, permission for the task and an eligible Grok Bot or Grok account. Workspace administrators may control which connections are allowed.

## Connect Grok Bot

Grok Bot is the desktop/mobile Bot product, with its own plugin connections. Its setup is separate from Grok web.

1. Open the Bot you want to use and ask it to add DoorOps as a custom **Remote HTTPS MCP** connection.
2. Give it the name **DoorOps** and URL **`https://doorops.com/mcp/connect`**. Use OAuth sign-in.
3. Open the authorization card and finish signing in to DoorOps in your browser. Check the company and requested access before allowing the connection.
4. Attach DoorOps to the task when needed, using the Bot's connector picker or `@` menu.

You can copy this first message:

> Connect DoorOps using the remote MCP server https://doorops.com/mcp/connect with OAuth. Ask me to sign in, then tell me my connected company and role. Show the exact proposal and ask me to confirm before creating, editing, scheduling, sending, merging or deleting anything.

For a Team Bot, an owner can add a custom Remote HTTPS server to the Bot's plugins. Each person signs in with their own DoorOps account; team connector policy still applies.

## Connect Grok web

1. Open [grok.com/connectors](https://grok.com/connectors).
2. Choose **New Connector → Custom**.
3. Enter **DoorOps** and **`https://doorops.com/mcp/connect`**, then complete OAuth sign-in.
4. Ask Grok which DoorOps company and role it is connected as.

On Grok Business or Enterprise, an admin provisions the connection first through **console.x.ai → Grok Business → Connectors**.

## Try these tasks

- “Show tomorrow's jobs and which ones are unassigned.”
- “Show this door's job and inspection history.”
- “Find submitted forms that need office review.”
- “Prepare updating this customer's phone number; show me the change before saving.”

Changes remain subject to your role, normal DoorOps rules and explicit confirmation. See the [MCP guide](/docs/developers/mcp) for previews, supported workflows and recovery.

## If something goes wrong

Check that the Bot used the authenticated **`/mcp/connect`** address, completed OAuth and selected the right company. If HTTP 429 appears, wait for the server's `Retry-After` period before retrying once. Refresh tools or reconnect if the provider reports an expired sign-in.

To stop access, disconnect the plugin/connector and revoke it in **DoorOps → Settings → Connected apps**.

Guidance checked **7 October 2026** against [Grok Bot connections](https://docs.x.ai/grok-bot/computer-and-apps), [Team Bot custom MCP support](https://docs.x.ai/grok-bot/team-bots), [Grok custom connectors](https://docs.x.ai/grok/connectors) and [Grok team connector administration](https://docs.x.ai/grok/connector-management). This is a custom connection; directory availability is separate.