Help Scout
drewburchfieldLABSCO SUMMARY
No account-wide off switch is the fact an administrator needs before anyone connects this.
Many enterprise connectors are gated by an admin — Box needs one, Atlassian follows existing controls, Amplitude has an org-level block. Help Scout does not: if someone can log in, they can connect an AI client to customer conversations. Whether that is acceptable is a policy question, but it should be answered deliberately rather than discovered. Per-user OAuth still means each connection is scoped to that person's own access.
What it is
Help Scout's endpoint over their support platform. They publish capability areas rather than a tool list, and suggest opening the connector in your client to see what it offers.
What you get
Searching conversations and pulling reports.
Requirements
OAuth 2.0 sign-in. Note the administrative gap Help Scout documents: there is no account-wide switch to disable MCP, so any user with a login can connect it.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Answering from past conversations
Search support history rather than asking a colleague who remembers.
02
Pulling a report
Reporting from the same connection as the conversation search.
03
Deciding a policy first
There is no admin switch, so agree who may connect before someone does.
BEFORE YOU INSTALL
What to know first
Requires
- an MCP client that can reach a remote endpoint
- A Help Scout account on the Standard, Plus or Pro plan, signed in over OAuth
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://mcp.helpscout.net/mcpRequirements
- OAuth 2.0 — you log in on Help Scout's own page and approve access
