Intercom Connector

How to Get It

Trust Signals Auto-scanned

Not yet scanned. Learn how to check this tool yourself.

Data & Access

Community Pulse New

No community discussions found yet. This doesn't mean the tool isn't good — it may be new or serve a niche use case.

Reviewer notes

Auto-scanned review. These are observations, not a security certification.

Fetched https://claude.com/connectors/intercom directly. GA across all Claude surfaces, points to Intercom's own MCP developer guides and privacy/support pages — reasonably client-ready, though the page itself doesn't state the auth method (only inferred as likely OAuth, not confirmed). Breadth is solid within support/CX teams (conversation search, contact lookup, custom-attribute filtering) but doesn't extend beyond that function — a 3. Intercom is an established, mature SaaS company (well over a decade in market, large customer base) — reliability 4, not the top tier of a public-company giant. Read-only scope is the main security positive: no write/mutate actions are documented, which meaningfully lowers risk versus write-capable connectors — security 4, held back only by undocumented auth/scopes on the page itself. | Sentiment: No significant community signal found — WebSearch and firecrawl search were both unavailable (quota/credits exhausted) during this evaluation. | Ensemble: median of 103 independent doc+sentiment evaluations (official-coverage sweep 2026-07-23).

Things to check

• Auth method not explicitly stated on the connector page (I inferred 'likely OAuth' but did not verify it); no enterprise/security specifics documented there.

How to evaluate tools before deploying →

Data shown here comes from public APIs and automated scanning. Reviewer notes reflect one person's experience. This is not a security certification or legal recommendation. Always evaluate tools according to your own organization's policies.

Evaluation

Fetched https://claude.com/connectors/intercom directly. GA across all Claude surfaces, points to Intercom's own MCP developer guides and privacy/support pages — reasonably client-ready, though the page itself doesn't state the auth method (only inferred as likely OAuth, not confirmed). Breadth is solid within support/CX teams (conversation search, contact lookup, custom-attribute filtering) but doesn't extend beyond that function — a 3. Intercom is an established, mature SaaS company (well over a decade in market, large customer base) — reliability 4, not the top tier of a public-company giant. Read-only scope is the main security positive: no write/mutate actions are documented, which meaningfully lowers risk versus write-capable connectors — security 4, held back only by undocumented auth/scopes on the page itself. | Sentiment: No significant community signal found — WebSearch and firecrawl search were both unavailable (quota/credits exhausted) during this evaluation. | Ensemble: median of 103 independent doc+sentiment evaluations (official-coverage sweep 2026-07-23).