This MCP server provides AI assistants with direct access to Help Scout inboxes, allowing them to search tickets, pull customer context, and monitor conversations efficiently.
From the registry: Search Help Scout conversations, customers, organizations, threads, and inboxes with AI assistants
Please install the `help-scout-mcp` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **Help Scout private app** — Create a private app in Help Scout My Apps with at least read access to Mailboxes, Conversations, Customers, and Organizations (https://secure.helpscout.net/users/apps)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["help-scout-mcp-server"]
- required environment variables:
- `HELPSCOUT_APP_ID`: Help Scout App ID (OAuth2 client ID) (example: `<your-helpscout-app-id>`)
- `HELPSCOUT_APP_SECRET`: Help Scout App Secret (example: `<your-helpscout-app-secret>`)
- optional environment variables:
- `HELPSCOUT_DEFAULT_INBOX_ID`: Scope searches to a specific inbox (example: `<your-inbox-id>`)
- `HELPSCOUT_BASE_URL`: Help Scout API endpoint (example: `https://api.helpscout.net/v2/`)
- `REDACT_MESSAGE_CONTENT`: Hide message bodies in responses (example: `false`)
- `CACHE_TTL_SECONDS`: Cache duration for API responses (example: `300`)
- `LOG_LEVEL`: Logging verbosity (example: `info`)
Note: Uses OAuth2 Client Credentials flow. Also available as a Docker image.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.HELPSCOUT_APP_IDrequiredApp ID from Help Scout My Apps.HELPSCOUT_APP_SECRETrequiredApp Secret from Help Scout My Apps.Lightweight DMARC parser: auto-fetch email reports, visualize compliance in a single all-in-one app