Category ยท 6 integrations
Connection guides integrations
Use TestingOps from the apps you already work in. These are setup guides: you connect the app to TestingOps, and the app calls TestingOps.
This is the opposite direction to MCP tools for agents. Here an outside app, such as ChatGPT or an editor, uses TestingOps as a tool.
Compare
How these tools differ
| Tool | What TestingOps does with it | Connection |
|---|---|---|
| Google Gemini | Covers two roles: agents run on your Gemini key, and Gemini CLI can call TestingOps over MCP. | Model provider, Connection guide Available |
| Claude | claude.ai and Claude Desktop add TestingOps as a custom connector with sign-in; Claude Code can also send an access key. | Connection guide Setup guide |
| ChatGPT | Sign-in only in the TestingOps guide; writing depends on the ChatGPT plan, and workspace admins publish the connector. | Connection guide Setup guide |
| VS Code & Cursor | An HTTP MCP server in the editor's own configuration with an access key; works with a self-hosted TestingOps the developer's machine can reach. | Connection guide Setup guide |
| Microsoft Teams & Copilot | No TestingOps Teams app: your own Copilot Studio agent calls TestingOps, with sign-in or an access key. | Connection guide Setup guide |
| Zoom | Needs a Zoom Marketplace app your own admin builds and submits; TestingOps does not read Zoom meetings or recordings. | Connection guide Setup guide |
Integrations in this category
Google Gemini
Agents can run on your Gemini API key, and Gemini CLI can use TestingOps over MCP: two separate connections.
Model providerConnection guideAvailableClaude
Add TestingOps to Claude as a custom connector, or to Claude Code as an HTTP MCP server, and work with runs, cases and defects from a chat.
Connection guideSetup guideChatGPT
Add TestingOps to ChatGPT as a custom MCP server and sign in, then ask about release readiness, existing cases and runs.
Connection guideSetup guideVS Code & Cursor
Add TestingOps to your editor's MCP configuration so its agent can read failing cases, check a change's impact and update cases.
Connection guideSetup guideMicrosoft Teams & Copilot
Build a Copilot Studio agent with TestingOps as its MCP tool and publish it to Teams and Microsoft 365 Copilot.
Connection guideSetup guideZoom
Your Zoom admin builds a Marketplace app that points at the TestingOps MCP server, so an AI Studio custom agent can ask about your tests.
Connection guideSetup guide
Other categories
Issue trackers, wikis and code
Requirements, work items, documentation and code changes are where test design starts. These connections give TestingOps agents that context and, where supported, a place to report back.
Test management
Keep your test management tool as the system of record. TestingOps can send cases with their steps, bring existing cases into its knowledge base and report run results where the tool supports it.
Design tools
Screens, flows and workshop boards describe the intended behaviour before any code exists. These connections bring that material into the knowledge base that agents write test cases from.
Test execution
TestingOps runs test cases on an execution provider and brings back results, steps and evidence. Which providers a workspace can use is decided by its execution policy.
Low-code platforms
Low-code platforms keep the application as a model: data, screens and logic in a structured form. Reading that model lets agents design tests around what the application actually contains.
Process models (BPMN)
A business process model already describes the paths a case can take. TestingOps turns BPMN 2.0 elements into bounded test scenario candidates for review.
App markets
Store reviews show where real users struggle. TestingOps turns them into insights for the knowledge base: themes, version-level signals and test ideas.
AI model providers
Choose the model provider your agents run on and use your own account and API key.
MCP tools for agents
These connections run in one direction: your TestingOps agents call an external tool through the Model Context Protocol (MCP) when a task needs it.
Private networks
Many test environments are only reachable inside a company network. These options let test runs reach them without opening the environment to the internet.