MCP server for Help Scout with full read coverage and opt-in write support: conversations, customers, organizations, reports, metadata, and Docs
Most developer tooling work still happens through a UI a human drives. Help Scout MCP server moves it into the conversation instead. MCP server for Help Scout with full read coverage and opt-in write support: conversations, customers, organizations, reports, metadata, and Docs through a compact gateway tool surface.
An MCP server that gives AI assistants direct access to your Help Scout inboxes, conversations, customers, organizations, threads, and Docs knowledge base. Search tickets, pull customer and account context, inspect articles, spot patterns, and get answers without leaving your editor or chat window.
The server publishes 3 tools. What each one is for:
search_help_scout — Find operations by intent ("customer conversation history", "happiness report")describe_help_scout — Load the full input schemas for the operations you selectedread_help_scout — Execute one operation: { "name": "getThreads", "arguments": { ... } }Configuration is passed through the environment: HELPSCOUT_APP_ID, HELPSCOUT_APP_SECRET, HELPSCOUT_DOCS_API_KEY, HELPSCOUT_CLIENT_ID, HELPSCOUT_CLIENT_SECRET, HELPSCOUT_DEFAULT_INBOX_ID, HELPSCOUT_BASE_URL, HELPSCOUT_DOCS_BASE_URL. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
help-scout-mcp-server on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.
Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Help Scout's toolset — search_help_scout, describe_help_scout, read_help_scout — is a fair guide to whether it matches your workflow. It is maintained by drewburchfield; worth a glance at recent repository activity before you build anything load-bearing on it.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| search_help_scout | Find operations by intent ("customer conversation history", "happiness report") |
| describe_help_scout | Load the full input schemas for the operations you selected |
| read_help_scout | Execute one operation: { "name": "getThreads", "arguments": { ... } } |
{
"mcpServers": {
"help-scout": {
"command": "npx",
"args": ["-y", "help-scout-mcp-server"],
"env": {
"HELPSCOUT_APP_ID": "your-value",
"HELPSCOUT_APP_SECRET": "your-value",
"HELPSCOUT_DOCS_API_KEY": "your-value",
"HELPSCOUT_CLIENT_ID": "your-value",
"HELPSCOUT_CLIENT_SECRET": "your-value",
"HELPSCOUT_DEFAULT_INBOX_ID": "your-value",
"HELPSCOUT_BASE_URL": "your-value",
"HELPSCOUT_DOCS_BASE_URL": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| HELPSCOUT_APP_ID | Configuration value read at startup. | Optional |
| HELPSCOUT_APP_SECRET | Credential the server authenticates with. | Yes |
| HELPSCOUT_DOCS_API_KEY | Credential the server authenticates with. | Yes |
| HELPSCOUT_CLIENT_ID | Configuration value read at startup. | Optional |
| HELPSCOUT_CLIENT_SECRET | Credential the server authenticates with. | Yes |
| HELPSCOUT_DEFAULT_INBOX_ID | Configuration value read at startup. | Optional |
| HELPSCOUT_BASE_URL | Endpoint or connection string the server talks to. | Yes |
| HELPSCOUT_DOCS_BASE_URL | Endpoint or connection string the server talks to. | Yes |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.