Grok Bot for Help Scout: Answer the Queue, Skip the Login
Want a Grok Bot working your Help Scout mailboxes? Connect Help Scout to Carly with your app credentials, add the Carly connector to Grok Bot once, and every Bot works your mailboxes through one connection that names the mailbox on every action and can hold customer replies for approval.
There is no Help Scout plugin in Cursor’s marketplace, which is where Grok Bot gets its tools. Help Scout’s own MCP server exists, but it cannot send a reply, add a note or change a tag. That leaves signing a Bot into a Help Scout seat in the shared browser, where every Bot you run inherits the login.
The quick answer: put Help Scout and your support address in Carly, then point Grok Bot at Carly. No shared password.
1. Connect Help Scout to Carly
Help Scout’s Inbox API (still called Mailbox API 2.0 in older docs) uses an OAuth2 app you create yourself.
- In Help Scout, open Your Profile, then My Apps, and click Create My App.
- Name it (for example “Carly”). Help Scout gives you an App ID and an App Secret. Carly uses them through Help Scout’s client credentials flow, the one Help Scout documents for internal integrations.
- Sign in at carlyassistant.com.
- Paste your API key into Carly on the integrations page. For Help Scout, that means the App ID and App Secret.
- On the same page, connect the mailbox your customers write to: find Gmail or Outlook, click Connect.
Two things to know first. Help Scout lists API access on its Standard, Plus and Pro plans, with the rate limit rising by plan. And the credentials act as the Help Scout user who created the app, so create it from a seat that can see all of the mailboxes the Bot should work, and nothing more.
Carly connects to thousands of apps, so add Slack for escalations, Stripe for refund lookups, and Google Calendar or Outlook Calendar for callbacks while you are there. If you also want Help Scout’s official MCP server alongside (useful for its reports), add it in Carly under Integrations → MCP servers.
2. Add Carly to Grok Bot
- Select Plugins in the Grok Bot sidebar, or tap your avatar and choose Plugins on mobile.
- Add Carly’s remote MCP server,
https://carlyassistant.com/mcp/. - Finish the authorization in the browser tab that opens. If it sits on Waiting for authorization, use Reopen.
- Sign in to the Carly account holding your Help Scout connection.
- Confirm Carly appears under Installed.
The App Secret stays in Carly. No Bot ever sees a Help Scout password, and none of them needs a browser session signed into your help desk.
What one Bot can do afterwards
- Triage new conversations. Read every unassigned thread across all of your mailboxes, tag by topic and urgency, and assign by rule (“billing goes to Emily, bug reports go to Josh”).
- Reply from a real support address. Draft and send answers from support@ through your connected Gmail or Outlook, threaded under the customer’s message, with the mailbox named on the action.
- Chase pending threads. Find conversations waiting on the customer for three days and send a polite nudge, then close the ones that stay quiet.
- Send a daily digest per mailbox. Open count, oldest unanswered customer, and what closed yesterday, emailed to the team at 8am.
- Escalate by rule. Anything mentioning a chargeback, a cancellation, or an account on your VIP list goes to Slack with a summary instead of an auto-reply.
Put a Require approval rule on external sends while you build trust. Carly holds each customer reply until you approve it, which is the preview a Grok Bot routine does not give you. The same triage also runs as a workflow described in plain English with no Bot open, or you can hand it to a named Carly agent with its own email address that Claire on your team CCs on hard threads.
Help Scout has its own AI layer too. AI Answers is an add-on agent billed per resolution, and AI Drafts writes suggested replies from past conversations and help content on the Plus and Pro plans. Those work inside Help Scout; Carly is what lets a Grok Bot act on the mailbox and everything around it.
The shared browser route, and what it costs you
SpaceXAI’s docs say to prefer a connector where one exists and to use the browser for services without one. For Help Scout, signing a Bot into the web app is the only way it can reply to a customer today. Here is what comes with it.
Every Bot gets the seat. All Bots on your account share one cloud computer, with shared browser sessions, cookies and credentials. SpaceXAI calls the separate screens “separate work surfaces, not separate security boundaries.” The Bot you asked to tidy tags can also send a refund promise.
A seat for a Bot. Help Scout bills per user, so a dedicated login for the Bot is another seat, and sharing a human’s login means every Bot acts as that person.
No dry run. Grok Bot has Auto-review rules (“ask first before sending any external email”), but SpaceXAI calls Auto Review model-based and says an approval does not reverse work already done. Nothing previews what a routine will click before it runs.
Sessions drop mid-task. When the Help Scout session expires halfway through a queue, the Bot stops or clicks into a login screen, and you find out afterwards which replies went out.
Help Scout’s MCP does not fill the gap. Grok Bot accepts remote MCP servers, so you can add Help Scout’s official one directly. Help Scout’s own docs say new connections are read-only: the agent “can’t reply to customers, add notes, change tags, or edit Docs articles,” with write actions on the roadmap and no date. Help Scout also notes there is no account-wide switch to turn MCP off.
Grok Bot’s shared browser next to Carly
| Need | Grok Bot’s shared browser | Carly connector |
|---|---|---|
| Setup | Sign a Bot into a Help Scout seat | Create an app in Help Scout, paste two credentials |
| Reply to a customer | Yes, by clicking through the UI | Yes, from your support address |
| Tag, assign, add notes | Yes, by clicking | Yes |
| Keep the login away from other Bots | No, every Bot shares the session | Yes, credentials stay in Carly |
| Approval before a customer send | Model-based Auto Review on a click | Require approval rules on the send itself |
| Survive a session timeout | Stops mid-task | Yes, API connection, no browser session |
| Gmail or Outlook support address alongside | Another shared login | Yes, same connection list |
| Keeps running on a schedule | Routines on the shared machine | Workflows and agents, with or without a Bot |
Carly offers free Zapier-style workflows; AI agents from $35/month.
Quick fixes
| Problem | Fix |
|---|---|
| No Help Scout plugin in Grok Bot’s Plugins list | Connect Help Scout in Carly and add the Carly connector |
| Help Scout’s MCP can read but not reply | Send replies through Carly; keep Help Scout’s MCP for reports if you like |
| 401 from Help Scout after connecting | The app’s owner must be an active, invited user; recreate the app from a current seat |
| Bot misses a mailbox | The app sees what its owner sees; grant that user the mailbox in Help Scout |
| Replies going out before review | Add a Require approval rule for external email |
Frequently asked questions
Does Grok Bot have a Help Scout integration?
Not in Cursor’s plugin marketplace, which is where Grok Bot’s plugins come from. You can add Help Scout’s official MCP server as a remote server, but it is read-only for new connections. Connecting Help Scout to Carly gives a Bot read and write access through one connector.
Can Grok Bot reply to Help Scout conversations?
Only by clicking through Help Scout in the shared browser, signed in as a user. Through Carly, the Bot sends the reply from your support address, and an approval rule can hold it for review first.
Which Help Scout plan do I need?
Help Scout lists API access on Standard, Plus and Pro. Carly works with any of them. On the Free plan, confirm API access before you create the app. If your setup needs a closer look, book a call with the Carly team.
Is it safe to give Grok Bot a Help Scout login?
Every Bot on your account shares one cloud computer, including browser sessions and credentials, so whatever one Bot can reach, all of them can. Keeping Help Scout in Carly means the login is never in that browser, and approval rules sit in front of customer sends.
Can one Bot cover several Help Scout mailboxes and Gmail?
Yes. Connect all of them to Carly and one Bot works across all of them, with every action naming its mailbox. Get started.
Related: Grok Bot · Grok Bot for HubSpot Service Hub · Grok Bot for Front · Multiple Gmail accounts in Grok Bot · Best Help Scout integrations · Claude and Help Scout
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
