Connect Help Scout to Claude Code

Let Claude draft replies, leave notes, and move conversations in Help Scout. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Help Scout to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Help Scout, you add a Help Scout MCP server: a small hosted service that exposes Help Scout's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Help Scout account. No API keys pasted into config files.

claude mcp add --transport http help-scout https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Help Scout once connected?

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

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Help Scout access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Help Scout API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Help Scout changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Help Scout connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Help Scout connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Help Scout account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Help Scout's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Help Scout?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Help Scout account it signs in with. Revoking access is one click in Help Scout.

More on the Help Scout connector

Help Scout connector for claude.ai Zendesk + Claude Code Freshdesk + Claude Code ServiceNow + Claude Code

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.

Build my connector Talk to us