| FMRS | 67 / 100 · C | 75 / 100 · B |
|---|
| Reliability | 9 / 20 | 10 / 20 |
|---|
| Security and permissions | 15 / 20 | 16 / 20 |
|---|
| Maintenance | 12 / 20 | 18 / 20 |
|---|
| Documentation | 17 / 20 | 17 / 20 |
|---|
| Setup experience | 14 / 20 | 14 / 20 |
|---|
| Best for | - Support teams using Help Scout who want AI assistants (especially Claude) to query tickets, customers, and knowledge base quickly
- Engineers who want customer context without leaving their editor or chat window
- Security-conscious teams needing read-by-default, auditable opt-in writes
| - Biomedical researchers
- Clinicians
- AI agents that need efficient access to biomedical literature and data analysis
|
|---|
| Not for | - Teams not using Help Scout as their help desk
- Environments unwilling to grant AI access to support data
- Users expecting out-of-the-box email sending, deletes, or admin config writes (deliberately not exposed)
| - Users needing to write to upstream databases (read-only)
- Users requiring direct access to closed datasets (e.g., COSMIC is not directly integrated)
- Users expecting all advanced features without API keys
|
|---|
| Required permissions | - Help Scout OAuth2 App ID and App Secret (required; authenticates as the creating user with their permissions)
- Optional: HELPSCOUT_DEFAULT_INBOX_ID to scope searches
- Optional: HELPSCOUT_DOCS_API_KEY for Docs knowledge base tools
- Optional: HELPSCOUT_ENABLE_WRITES and HELPSCOUT_ENABLE_CUSTOMER_VISIBLE_WRITES for write operations
| - Requires internet access to query public biomedical APIs
- Optional API keys (NCBI, Semantic Scholar, OpenFDA, etc.) to improve rate limits or unlock features
- Local read/write access for skills, cache, and local study data (e.g., `~/.local/share/biomcp`)
|
|---|
| Risks and side effects | - AI can access all support data (conversation content, customer and organization info); credential leakage risks data exposure
- Message content is included by default; REDACT_MESSAGE_CONTENT is not a compliance boundary and does not remove all customer identifiers
- When writes are enabled, the server can modify conversation status, tags, assignments, etc.; tier-2 operations (sendReply/publishDraft) email customers and require care despite confirmation mechanisms
- Help Scout OAuth2 has no separate scope selection; the app acts with the creator's permissions, so shared credentials widen impact
| - Upstream API rate limits may affect performance
- Some data sources (e.g., KEGG) have licensing terms that restrict non-academic use
- Features requiring API keys (e.g., OncoKB) may be incomplete without them
- Local binary installations need regular updates for compatibility
|
|---|
| Supported clients | Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, Continue, Goose, Claude Cowork, Codex, Gemini CLI, OpenCode | Claude Desktop, Claude Code, Codex, Other MCP stdio clients |
|---|
| Tools | 4 | 11 |
|---|