Full read-write Claude connector for Help Scout
Let Claude draft replies, leave notes, and move conversations in Help Scout
Stop tab-switching to triage your shared inbox. Claude reads the conversation, drafts the reply in place, leaves a private note for the next agent, sets status, tags, and assignment, and sends only once you approve.
Help Scout is a shared-inbox helpdesk where teams handle customer conversations, assign work, and keep a knowledge base. People want Claude to do more than read conversations: to draft and send replies, leave private notes, set status and tags, and assign work without leaving the thread.
What is a Help Scout MCP server?
A Help Scout MCP server is a small hosted service that exposes Help Scout's data and actions to Claude over the Model Context Protocol, so Claude can tickets and customer conversations inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Help Scout's current connector do today?
Today, Help Scout has no first-party Claude connector, so any access goes through a custom MCP server. Generic setups tend to lean on reading conversations and search, and rarely cover the write actions that move work, like sending replies, changing status, leaving notes, assigning, or tagging inside the conversation where the work lives.
What does full read-write Help Scout access unlock?
Full read-write Help Scout access lets Claude draft a reply on the right conversation, leave a private note for the next agent, set status and tags, and assign to the correct person, all after you approve. The triage and follow-up that used to mean tab-switching happen where the conversation already lives.
- Draft a reply on a conversation, preserving the customer and message history
- Add a private note with context for the next agent
- Set a conversation's status to active, pending, or closed as it moves
- Apply tags and assign the conversation to the right person or team
- Search conversations matching a query and propose batched responses
- Send a drafted reply to the customer once you approve it
Can Claude reply to Help Scout conversations, not just read them?
Yes. Claude can reply to Help Scout conversations by drafting the response on the original thread, with the customer and message history intact. It can also leave a private note for the next agent. Sending the reply to the customer is a separate, gated action that runs only after you approve it.
Can Claude triage and route conversations in Help Scout?
Claude can triage and route conversations in Help Scout by searching threads matching a query, setting status to active, pending, or closed, applying tags, and assigning to the right person or team. The reads and routing flow freely while customer-facing replies wait for your confirmation before anything goes out.
Will Claude send Help Scout replies without my approval?
No. Sending a Help Scout reply and closing a conversation are gated write actions that run only after you confirm them. Claude can prepare the reply, stage the status change, and queue the note, but outbound and destructive steps always wait for a human, so nothing reaches a customer by surprise.
How a Help Scout connector works
We build a small MCP server that authenticates to Help Scout with OAuth over your account's existing permissions. Read tools (search, read conversation) and write tools (reply, note, set status, assign, tag) are separated, and outbound or destructive actions like sending a reply or closing a conversation require your confirmation. Claude only ever has the access your own Help Scout account already has.
Frequently asked questions
Can Claude reply to Help Scout conversations, not just read them?
Will Claude send Help Scout replies or close conversations without my approval?
Does the Help Scout connector get more access than my account has?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.