API Overview
MCP Integration

Connect Grok Bot to MoveRight

Use Grok Bot to look up jobs, run reports, check event status, and manage moves — all through the Model Context Protocol (MCP). Each Bot works on its own persistent computer, so it can check MoveRight data and act on it while you're away.

Contents

What is MCP? Prerequisites Connect Grok Bot Try It Out Troubleshooting

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI assistants like Grok Bot securely connect to external tools and data sources. When you connect a Bot to MoveRight via MCP, your Bot can:

  • Look up jobs by code, customer name, or status
  • Run and view operational reports
  • Check calendar event details and statuses
  • View charges, invoices, and transactions
  • Report issues straight to the Move Right dev team

Authentication uses OAuth 2.0 — when your Bot first connects, a browser window opens and you log in with your MoveRight credentials (password, magic link, or passkey). No API keys or tokens to manage, and your credentials are never stored inside the Bot itself.

Prerequisites

  • You must have logged in to MoveRight at least once. If you've never logged in to moveright.app, your account won't be linked to the authentication system and Grok Bot won't be able to connect. Log in at moveright.app first, then come back here.
  • A MoveRight account with an employee or admin role (customers cannot use MCP)
  • Grok Bot on desktop or mobile with a supported plan

Connect Grok Bot to MoveRight

Step 1 — Open the Bot you want to connect

Open the Grok Bot app and pick (or create) the Bot you want to give MoveRight access — for example your ops assistant. Connected apps are account-wide, so every Bot you run will be able to use MoveRight tools.

Step 2 — Add the MoveRight MCP server

In the Bot's chat, ask it to add the MoveRight MCP server, or open Connect apps yourself and choose the option to add an MCP server by URL.

MCP Server URL 
https://moveright.app/api/mcp

Step 3 — If asked for OAuth credentials, use these

If Grok Bot asks for an OAuth client ID and secret, paste in the values below. Grok Bot discovers the OAuth endpoints automatically on its own.

OAuth Client ID 
733e82be-07ad-4752-874e-1b2d943899e3
OAuth Client Secret 
4RQXtZdXz7lFkfzpKJqXvJoPy3Vl1lzXnmqpAzmuezE

Step 4 — Authorize the Bot in your browser

When the Bot requests authorization, a browser window opens — log in to Move Right using your password, magic link, or passkey, and approve the connection. Once you're logged in, you'll be redirected back to Grok Bot and the MoveRight app is connected.

TODO screenshot: Grok Bot connect apps — add MCP server by URL
Adding the MoveRight MCP server in Grok Bot

Step 5 — Confirm tools are available

From your next message, the Bot has access to MoveRight tools. Ask it something from the list below to confirm — if it answers with real job and schedule data from your zone, you're connected.

Try It Out

To confirm the connection is working, ask your Bot a few questions. Here are some good starters — the Bot will call MoveRight tools and answer with live data from your zone:

  • "Find the 5 most recent jobs that came in and summarize them for me."
  • "Pull an example report of my jobs for today."
  • "Build me a nice-looking report of my jobs for the day, and call out any red flags."
  • "Find job PHX-XQI-ZQB and walk me through what's happened on it so far."
  • "What's on the schedule for tomorrow?"
  • "The estimate template tax breakdown looks wrong on one of my jobs — report it to the Move Right dev team."

Because your Bot runs on its own computer, you can go further than one-off questions: ask it to check your jobs every morning and message you a summary, or have it watch for red flags and report back — the MoveRight connection stays alive between tasks.

If the Bot says it can't reach MoveRight, see Troubleshooting below.

Troubleshooting

"Authorization with Move Right failed"

This usually means your MoveRight account doesn't have an employee or admin role, or your account hasn't been linked to the authentication system yet. Make sure you've logged in to MoveRight at least once, and contact your MoveRight administrator to verify your account has the correct role and permissions.

"Role required" or "Current zone not set"

Your MoveRight user may have duplicate accounts (e.g. a customer profile and an employee profile with the same email). Contact support to have the accounts consolidated.

"Invalid redirect_uri"

The redirect URI Grok Bot uses must be registered with our auth provider. This is already configured — if you see this error, it may be a temporary issue or a newly updated Grok Bot client. Try again, and if it persists, contact support.

Server connection fails or the Bot says it can't reach MoveRight

Double-check that the MCP Server URL is exactly https://moveright.app/api/mcp. If the URL is right but the Bot still can't connect, remove the server in Connect apps and re-add it, then complete the browser authorization again.

Need more help?

Contact MoveRight support at support@moveright.app or through the in-app chat.