TestingOps.ai

MCP tools for agents · MCP tool for agents

Intercom and TestingOps: support conversations as test input

Connect Intercom's MCP server and TestingOps agents can read what customers report in support conversations and turn it into reproduction steps and test cases for review.

  • MCP tool for agents
  • Available with limits
Request a demo Intercom MCP server
Connection
MCP tool for agents
Writes back
Only after a person approves
Last checked
7 Nov 2026

In short

Intercom and TestingOps in short

The Intercom connection is an MCP tool for TestingOps agents, set up with the access token of a private app in your Intercom Developer Hub that has read permissions only.

Agents can search and read support conversations, contacts, companies and help articles, for example to collect the steps customers describe for a problem after a release and draft cases that reproduce it.

Only US-hosted workspaces can be connected today: EU workspaces cannot authenticate through Your own MCP server, and Intercom's server does not support AU workspaces.

What it does

What it does for your testing

  1. 1

    Customer reports become reproduction steps

    Input
    Support conversations about a problem
    TestingOps
    Agents can read the conversations and extract the steps and conditions customers describe
    Output
    Draft reproduction steps and cases for review
  2. 2

    Documented behaviour from help articles

    Input
    Your help center articles
    TestingOps
    Agents can read how a feature is described to customers
    Output
    Expected results that match what customers are told
  3. 3

    A defect with customer impact

    Input
    A confirmed defect and related conversations
    TestingOps
    Agents can find and cite the conversations that mention it
    Output
    A defect report that shows how often customers ran into the problem

Step by step

How it works

  1. Create a private app with read permissionsIn Intercom's Developer Hub (the teammate needs Can access developer hub), create an app for your workspace and, under Configure → Authentication, keep only the permissions agents need: Read conversations, Read and list users and companies, Read and list articles.
  2. Connect its access tokenPick Intercom under Extra tools your agents may use in Integrations → API & MCP, paste the access token into Intercom access token and select Connect.
  3. Agents read during a taskWhen a task needs customer context, an agent can search and read conversations through TestingOps; the token stays on the TestingOps server.

If you change the app's permissions later, regenerate the token in Intercom and paste the new one.

Connect

Setup

  1. In Intercom, open the Developer Hub and select New app; name it, pick the workspace and select Create app.
  2. Under Configure → Authentication, keep only Read and list users and companies, Read conversations and Read and list articles, and save.
  3. Copy the Access token shown on the same page.
  4. In TestingOps, as customer admin, open Integrations → API & MCP, pick Intercom under Extra tools your agents may use (outgoing, over MCP), paste the token into Intercom access token and select Connect.

Documentation: Intercom MCP server

Where you connect it in TestingOps: Integrations → API & MCP → Extra tools your agents may use → Intercom

Use cases

Use cases

Turn a support spike into regression cases

Trigger
Support sees many conversations about failed password resets after a release
Uses
The conversations that mention the problem
Agent activity
Can read them, extract the steps and devices customers describe and draft cases that reproduce the problem
Result
Draft cases tied to real customer reports, ready for review

Reproduce a reported bug

Trigger
A support agent escalates a conversation as a possible bug
Uses
The conversation and the contact's details
Agent activity
Can read the customer's steps and environment and draft a reproduction for a run
Result
A reproducible case, or a note that the steps could not be reproduced

Check what customers are told

Trigger
A case's expected result is unclear
Uses
Help center articles
Agent activity
Can read the article that describes the feature
Result
An expected result in line with the help center

Capabilities

Capabilities and limits

What is read

With the read permissions from the setup: conversations, contacts (users), companies and help articles

What is produced

Customer context, reproduction steps and draft cases in agents' output; nothing is stored in TestingOps by the tool itself

Where it can write

  • Nothing with the read-only permissions from the setup steps
  • Intercom's server also has tools that add internal notes or create and update articles; with a broader token they ask first in TestingOps, and an approved call still changes your workspace, so keep the token read-only

How it connects

Intercom's hosted MCP server for US workspaces (https://mcp.intercom.com/mcp) with the private app's access token in the Authorization header

Account and permissions

  • A private app in your Intercom Developer Hub with read permissions, and its access token
  • Customer admin (or Manage integrations) rights in TestingOps; the tool is visible only to agents working on your organisation's projects

Limits

  • US-hosted workspaces only; EU cannot authenticate through Your own MCP server yet, and Intercom does not support AU
  • Conversations can contain personal data, and agents may quote conversation text in their output; TestingOps masks secrets such as keys in tool results, not personal data
  • Agents running on Grok receive no MCP tools

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

After a mobile release, support at a subscription service sees conversations about payments failing on one Android version. With Intercom connected through a read-only token, an agent can read those conversations and collect the device and app version each customer mentions.

It drafts two cases for that Android version and payment method, and the test lead adds them to the next mobile run.

Frequently asked questions

Our Intercom workspace is hosted in the EU. Can we connect it?

Not yet. Intercom's EU server has its own address, but Your own MCP server takes only an address, so the token cannot be sent. AU workspaces are not supported by Intercom's MCP server.

Can agents reply to customers?

Not with the read-only permissions from the setup. Keep it that way: Intercom's server also has tools that write, and not all of their names mark them as writes in TestingOps.

What about personal data in conversations?

Agents read what the token allows and may quote parts of a conversation in a case or analysis. TestingOps does not filter personal data out of tool results, so limit the app's permissions to what agents need.

Does TestingOps import our conversations?

No. Agents read them through the tool during a task; there is no background import.

Next step

Request a demo to see how agents can turn support conversations into cases for review.

Request a demoMore mcp tools integrations