Most enterprise connectors here 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.
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.
Searching conversations and pulling reports, per their documentation. The endpoint requires OAuth before listing, so we could not enumerate it.
OAuth 2.0 bearer, with standard discovery metadata. 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.
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen