TestingOps.ai

Connection guides · Connection guide

Zoom and TestingOps: test questions from Zoom AI Companion

Zoom AI Companion reaches MCP servers through a Zoom Marketplace app. With an app your Zoom admin builds, a custom agent in AI Studio can call TestingOps, while TestingOps itself reads nothing from Zoom.

  • Connection guide
  • Setup guide
Request a demo Zoom: connect to an external MCP server
Connection
Connection guide
Writes back
Depends on the access you grant
Last checked
7 Nov 2026

In short

Zoom and TestingOps in short

There is no ready-made TestingOps app for Zoom: your Zoom admin or developer builds a General app in the Zoom App Marketplace, adds the TestingOps MCP endpoint, which ends in /api/mcp/v1, as an MCP server, submits the app for Zoom's review and adds it as a tool to a custom agent in AI Studio.

The Zoom custom agent then calls TestingOps tools as the person who connected it, for example to report on a run or list open defects.

The opposite direction is not available: TestingOps agents cannot read Zoom meetings, recordings or chat.

What it does

What it does for your testing

  1. 1

    Defect status inside an AI Companion agent

    Input
    A question to the custom agent: which defects are still open for this release?
    TestingOps
    Returns the defects and their status through the agent's TestingOps tool
    Output
    The open defects in the agent's reply
  2. 2

    A run summary before a call

    Input
    A request for the latest run's results
    TestingOps
    Returns the run's outcome and its failing cases
    Output
    A summary someone can bring to the meeting

Step by step

How it works

  1. Build a General appA Zoom admin or developer creates a General app in the Zoom App Marketplace; TestingOps does not publish one.
  2. Add TestingOps as an MCP serverIn the app's Connect section, on the MCP tab, add the endpoint from Integrations → API & MCP and let Zoom check the server.
  3. Submit the app for Zoom's reviewZoom reviews the app you submit, following its own rules for Marketplace apps.
  4. Add it to a custom agentIn AI Studio, add the app's MCP tool to a custom agent and authorise it.
  5. The agent calls TestingOpsWhen a question needs it, the agent calls TestingOps tools with the permissions of the TestingOps identity it signed in with.

The Zoom-side steps follow Zoom's documentation and can change. Nothing is installed on the TestingOps side: the app uses the same endpoint and sign-in as any other assistant.

Connect

Setup

  1. Copy the Endpoint (streamable HTTP) from the MCP server card under Integrations → API & MCP; the Zoom admin needs this address.
  2. In the Zoom App Marketplace, a Zoom admin or developer creates a General app (Develop → Build App).
  3. In the app's Connect section, on the MCP tab, add the endpoint as an MCP server and check it. Zoom offers dynamic client registration for MCP servers, which the TestingOps sign-in supports.
  4. Submit the app for Zoom's review, then add it as a tool to a custom agent in AI Studio and authorise it.
  5. When the app signs in, choose the company or customer and read only or read and write on the TestingOps consent page.

Documentation: Zoom: connect to an external MCP server

Where you connect it in TestingOps: Integrations → API & MCP → Connection guides → Zoom

Use cases

Use cases

Defect status for a release call

Trigger
A release manager prepares a release call in Zoom
Uses
Defects and their status
Agent activity
The custom agent lists the defects still open for the release
Result
The status at hand in AI Companion
Condition
The Zoom app must be approved and added to the agent

Latest run at a glance

Trigger
A team lead wants the outcome of the last regression run
Uses
Runs and their results
Agent activity
The agent returns the outcome and the failing cases
Result
A short run summary without opening TestingOps
Condition
Read only access is enough

Readiness question before a go-live meeting

Trigger
A product owner asks whether the release is ready
Uses
Release readiness assessment
Agent activity
The agent returns the recommendation with blockers and never-run cases
Result
An answer that names what was not tested
Condition
People make the release decision

Capabilities

Capabilities and limits

What is read

  • Through your Zoom app: the TestingOps tools available to the person who connected it, such as runs, results, defects and release readiness
  • Nothing from Zoom: meetings, recordings and chat are not read

What is produced

Answers in the AI Studio custom agent, built from TestingOps tool results

Where it can write

Nothing in Zoom. With read and write access, the same TestingOps write tools as other assistants, such as filing defects or starting runs.

How it connects

An MCP server entry in a Zoom Marketplace General app, used as a tool by an AI Studio custom agent

Account and permissions

  • Your Zoom admin or developer builds and submits the app
  • On the TestingOps side: sign-in on the consent page or an access key, with read only or read and write access

Limits

  • No TestingOps app in the Zoom App Marketplace
  • TestingOps agents cannot use Zoom meetings, recordings or chat as tools
  • The TestingOps endpoint must be reachable from Zoom over https
  • Tools only: no MCP resources or prompts

Example

Example: how a team uses it

Illustrative scenario, not a customer story.

A company's Zoom admin builds a General app named Test status, adds the TestingOps endpoint on its MCP tab and submits it. Once it is approved, the QA lead adds it to a custom agent in AI Studio and signs in with an account that has read only access.

Before the weekly release call, the release manager asks the agent which defects are still open. The agent answers from TestingOps with the open defects and their severity, and the call starts from that list.

Frequently asked questions

Can TestingOps read our Zoom meetings, recordings or chat?

No. That direction would need an app your Zoom admin builds for Zoom's own MCP servers, and TestingOps does not offer it. This guide covers the other direction: Zoom AI Companion calling TestingOps.

Is there a TestingOps app in the Zoom App Marketplace?

No. Your Zoom admin or developer builds a General app for your account and adds the TestingOps endpoint to it.

What can the custom agent do with TestingOps?

It uses the same TestingOps tools as other assistants, within the permissions of the person who connected it: read runs, results, defects and release readiness and, with read and write access, start runs or file defects.

How does the Zoom app sign in to TestingOps?

TestingOps accepts sign-in on its consent page, where clients register themselves, or an access key in the Authorization header. Which of the two your app uses is set in the app's authentication settings in Zoom.

Next step

Request a demo to talk through whether a Zoom AI Companion agent fits how your team reviews test status.

Request a demoMore connection guides integrations