Turnkey support for every site you run, with Grok Bot and muro

Running ten sites is fine until the visitors start writing. One asks about shipping on the shop, another hits a bug on the SaaS, a client's customer wants a quote. Each site has its own chat tool, or none, and the answers wait until you find a free hour.

The setup in this guide splits the work three ways. muro sits on every site: its AI answers visitors from your own docs in their language and hands the hard questions to a person. Every conversation lands in one inbox per business. Grok Bot, the always-on agent from xAI, connects to that inbox over MCP and does the reading: it triages, drafts replies, chases handoffs and sends you a short report. You keep the last word.

What Grok Bot is, briefly

Grok Bot (often written Grokbot) is xAI's agent product, launched in beta in August 2026. Instead of a chat window, each bot is a named agent with a job, its own cloud computer, a browser and a terminal, and it can run routines on a schedule. It talks to outside tools through connectors, and xAI documents a Custom connector for any MCP server reachable on the public internet. That last part is what lets it work a muro inbox.

Access comes with paid xAI and Cursor plans, and the bundles have moved since launch, so check what your own plan includes before you start. Grok Bot runs on xAI's models only, which matters for one decision further down: where your support data goes.

Who does what

Step 1: one workspace per business

In muro a workspace is one business or portfolio, and sites are the websites inside it. Each workspace has its own sites, one inbox for all of them, its own team, AI settings and knowledge, API keys and plan. If your client sites, your SaaS and your shops are run differently, give each its own workspace: the bot you connect to the SaaS inbox never sees a client's customers. Ten sites of the same business sit side by side in one workspace, each with its own widget.

Create a workspace from the name at the top of the sidebar. Solo covers up to 10 sites per workspace and Fleet is unlimited; the details are on pricing.

Step 2: put the widget on every site at once

Three ways, pick whichever matches how your sites are hosted.

• Cloudflare, no code. If your domains are on Cloudflare, open Sites and choose Add all from Cloudflare. Paste a scoped API token, tick the domains, and muro creates one site per domain and deploys a small Worker that adds the snippet to your HTML pages. The token is used for that request and never stored. On Cloudflare's free Workers plan every request to a routed domain counts toward a daily quota of 100,000; muro asks Cloudflare to skip the Worker once it runs out, so the sites stay up and the chat comes back the next day.
• From an agent in each repo. The MCP tools create_sites (up to 50 domains in one call) and get_install_snippet let an agent create the sites and paste the snippet into each codebase. The same exists over the REST API.
• By hand. Copy the one-line snippet from the site's Install block and paste it before </head>.

Each site keeps its own look: color, launcher icon and style, welcome message, language. You can set those in the dashboard or let the agent do it with update_site.

Step 3: teach muro's AI your answers

Before any bot touches the inbox, let muro's own AI take the easy questions. Import your docs or help center into the workspace, write a few lines of instructions per site (tone, policies, what never to promise), and turn on AI answers. When the answer is not in your docs, the AI says so and hands the conversation to a person, which shows up as a handoff in the inbox.

muro's AI runs on a monthly pool of credits, one credit per AI action, or without limit on your own Anthropic key. Grok Bot's work is separate: it runs on xAI's side and spends your xAI or Cursor plan, never your muro credits.

Step 4: connect Grok Bot to muro over MCP

muro hosts an MCP server at https://muro.chat/api/mcp (Streamable HTTP). It authenticates with a muro API key sent as Authorization: Bearer mr_live_….

Create the key

In the workspace, open MCP and API and create a key. Start with read only for the first week. Scope it to one site if the bot should only see that site, for example one client's shop.

Add the connector in Grok

1. Go to grok.com/connectors.
2. Click New Connector, then Custom.
3. Enter https://muro.chat/api/mcp and complete the authentication step with your muro key.
4. Ask your bot: "List my five most recent muro conversations." It should call list_conversations and answer with real threads.

From the Grok command line, a remote MCP server can be added with a static auth header:

export MURO_KEY=mr_live_your_key
grok mcp add --transport http muro https://muro.chat/api/mcp --header "Authorization: Bearer ${MURO_KEY}"
grok mcp doctor muro

And through the xAI API, the remote MCP tool takes the key in its authorization field, which is handy for your own scheduled job:

curl https://api.x.ai/v1/responses \
  -H "Content-Type: application/json" \
  -H "Authorization: Bearer $XAI_API_KEY" \
  -d '{
    "model": "grok-4.7",
    "input": [{ "role": "user", "content": "Summarize the open muro conversations that need a person." }],
    "tools": [{
      "type": "mcp",
      "server_url": "https://muro.chat/api/mcp",
      "server_label": "muro",
      "authorization": "'"$MURO_KEY"'",
      "allowed_tools": ["list_conversations", "get_conversation"]
    }]
  }'

allowed_tools keeps the bot to the tools a job needs, which also keeps the model's context small.

Step 5: give the bot a job and a schedule

Grok Bot works best with a narrow job description. Create a bot called something like Support desk and give it routines. A starting set:

1. Every morning: "In muro, list open conversations from the last 24 hours across all sites. Group them by site. Flag anything about payments, refunds, bugs or angry customers. Send me the list in five lines or fewer."
2. Twice a day: "Find open conversations tagged as handed off by the AI. For each, read the thread and write a draft reply as an internal note, not a reply to the visitor. Use only facts that appear in the thread or our docs."
3. Every Friday: "Count this week's conversations per site, list the five questions that came up most, and suggest one help article per question that would have answered it."

Drafting into internal notes keeps a person in the loop: you open the inbox, read the bot's draft next to the thread, and send it yourself. Once you trust its drafts for a site, give that site's key the write scope and let the bot send the replies you have approved.

What the bot can do in muro

Everything the bot does is attributed to the API key it used, so you can always tell which replies a model sent.

Guardrails worth keeping

• Read only first. A week of reports and internal-note drafts tells you how the bot behaves before it can message anyone.
• One key per business, scoped when it matters. A key scoped to one site physically cannot read another site's conversations.
• Keep approvals on for sends. Grok Bot can ask before acting; leave that on for send_reply until you have reasons to drop it.
• Know where the data goes. muro hosts its servers and database in Germany. When Grok Bot reads a conversation, that text goes to xAI to be processed on its side. If your visitors are in the EU, check that this fits your privacy policy and agreements before you connect a site.

What it costs

On muro: Solo is $19 a month for up to 10 sites with 1,000 AI credits, Fleet is $59 for unlimited sites with 3,000 credits, both after a 14-day trial with no card, and your whole team is included. MCP, the REST API and the Cloudflare install are on both. Grok Bot is billed by xAI or Cursor on your own plan.

Start with one business: create a workspace, put the widget on its sites, import the docs, then connect Grok Bot with a read-only key and ask it what came in this morning. When the drafts start sounding like you, add the next workspace.

1. 1xAI, Grok connectors: custom MCP connectors (accessed 2026-11-01)
2. 2xAI, Grok MCP servers (grok mcp add, static headers) (accessed 2026-11-01)
3. 3xAI, Remote MCP tools in the API (accessed 2026-11-01)
4. 4Vellum, Grok Bot breakdown (launch, schedules, approvals, access) (accessed 2026-11-01)
5. 5MindStudio, what Grokbot is (accessed 2026-11-01)