Claude + Help Scout: The Official Connector Is Read-Only
Yes, Claude can now read Help Scout through Help Scout’s official MCP server, but it can’t act on it. Help Scout runs the server at https://mcp.helpscout.net/mcp, and you add it to Claude as a custom connector (it isn’t in Anthropic’s Connectors Directory). New connections are read-only: Claude can find and summarize conversations, customers and Docs articles, but it can’t reply to customers, add notes or change tags.
So Claude can look things up, and someone still has to do the work. Help Scout also has a REST API, the Mailbox API v2, and an AI agent connected with your own API key can use it to act. Here’s what the official connector does, where it stops, and how to wire Help Scout up to an agent that works your queue while you’re away.
What Help Scout’s official connector does, and where it stops
Help Scout is a shared inbox and help desk built for customer support teams: conversations, mailboxes, and a Docs knowledge base. Its MCP server gives Claude official access to that data:
- Setup. In Claude, open Customize → Connectors, add a custom connector and paste
https://mcp.helpscout.net/mcp. The connector registers itself, and each teammate signs in with their own Help Scout account. On Claude Team and Enterprise, only an Owner can add custom connectors. - Plans. It works on Help Scout’s Standard, Plus and Pro plans (any plan with API access). Report tools need Plus or Pro.
- Read-only. New connections can find and summarize conversations, customers, mailbox data and Docs articles. They can’t reply to customers, add notes, change tags or edit Docs. Help Scout says write actions are on the roadmap, with no date yet.
That leaves support teams in one of two spots:
- Claude’s connector answers questions about your inbox inside a chat you start, but it can’t touch a conversation, and nothing starts because a ticket landed.
- No-code automation tools do list Help Scout, but they’re built for basic field-mapping triggers — “when a conversation is created, add a row” — not an agent that reads the thread, reasons about it, and drafts a real reply.
The detail that flips the answer: Help Scout already exposes a REST API with OAuth2 and API-key authentication. Your conversations, customers, and mailboxes are all reachable — you just need an agent willing to talk to it with your own credentials.
The part that changes the answer: bring your own API key
Carly connects to thousands of apps, Help Scout included. You paste a Help Scout API key into Carly, and because that key reaches the full Mailbox API, Carly can write as well as read.
You generate an API key in Help Scout, hand it to Carly, and Carly can read and act on your conversations as part of a real workflow — the same way it works with a natively supported app. No waiting for Help Scout to ship write access to its MCP server.
And because Carly runs in the cloud on triggers, this isn’t “answer me when I ask.” It’s inbox work that happens on its own, 24/7.
What you can automate once it’s connected
With Help Scout reachable through its API, an agent can handle the queue triage that usually eats a support rep’s morning:
- Triage and tag incoming conversations — read each new ticket, categorize it (billing, bug, how-to), apply tags, and set a priority the moment it lands.
- Draft context-aware replies — pull the customer’s history and your Docs articles, then draft a reply for a human to approve, or send it for known low-risk questions.
- Route to the right mailbox or teammate — assign conversations based on topic, language, or account tier instead of leaving them in a general queue.
- Summarize long threads — condense a back-and-forth into a two-line summary and suggested next step before anyone opens it.
- Tie the inbox to the rest of your stack — since the same agent handles email, calendar, and your CRM, logging a refund or creating a follow-up task becomes one step in the same workflow.
How to connect Help Scout to Carly
- In Help Scout, create an API key / OAuth2 app under your profile or company API settings to get credentials for the Mailbox API v2.
- Paste your API key into Carly on the integrations page.
- Describe the workflow in plain English — “when a new conversation comes in, tag it by topic and draft a reply from our Docs” — and Carly interviews you, then builds it.
Your key stays yours: rotate or revoke it in Help Scout whenever you like.
Claude connector vs. no-code tools vs. Carly
| Claude | No-code tools | Carly | |
|---|---|---|---|
| Official Help Scout connector | Yes, read-only (MCP) | Basic triggers | Via your API key |
| Reads & writes conversations | Reads only | Limited | Yes |
| Acts on triggers / events | No | Basic triggers | Yes, 24/7 in the cloud |
| Reasons over ticket + history | In chat only, if you paste it | No | Yes |
| Sends email as part of the flow | Draft-only | No | Yes (Gmail + Outlook) |
| Works while your laptop is closed | No | Yes | Yes |
Claude is a strong assistant inside a chat, and with Help Scout’s read-only connector it can look up and summarize your mailbox, but it can’t reply, tag or route. No-code tools can move data on simple triggers but won’t read a thread and write a real answer. Carly reaches Help Scout through your own API key and acts on it as part of a workflow that runs on its own.
Frequently Asked Questions
Does Claude integrate with Help Scout?
Yes, read-only. Help Scout runs an official MCP server (https://mcp.helpscout.net/mcp) that you add to Claude as a custom connector on Help Scout’s Standard, Plus or Pro plans. Claude can then find and summarize conversations, customers and Docs articles, but new connections can’t reply, add notes or change tags. To have an AI agent act on Help Scout, you need a tool that uses its REST API, like Carly, which connects with your own API key.
Does Help Scout have an API?
Yes. Help Scout exposes the Mailbox API v2, a RESTful API with OAuth2 and API-key authentication that supports reading and writing conversations, customers, mailboxes, and tags. That’s what lets an agent triage, tag, and reply to tickets programmatically.
Can I connect Help Scout to an AI agent?
Yes. Because Help Scout has a REST API, any agent that lets you bring your own API key can read and act on your conversations. Carly does this — you generate a key in Help Scout, add it to Carly, and it can then triage, tag, route, and draft replies automatically.
What can an AI agent actually do in Help Scout?
Triage and tag new conversations, draft context-aware replies from your Docs, route tickets to the right mailbox, summarize long threads, and log actions in your other tools — all triggered by a ticket arriving rather than you prompting in a chat.
How much does this cost?
Carly’s AI agents start at $35/month, and steps in a workflow that don’t use AI run free. Your Help Scout API access is part of your existing Help Scout plan.
More: Claude connectors · Best AI inbox management tools · Can Claude send emails · Claude vs Carly · Claude + beehiiv · Claude + Mercury · Claude + DealCloud · Best Help Scout integrations
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."
