Custom MCP integrations, network request checks, and shape drawing

Highlight
Featured this release
Connect your team's MCP tools to the AI chat
Register a remote MCP server and the chat agent discovers and calls its tools directly in conversation.
Add a server under Settings → Integrations → Custom MCP Integrations: authenticate with an API key or sign in with OAuth, and the chat agent picks up its tools automatically. Connections can be personal, so each teammate uses their own account, or shared across the whole project.

Per-tool permissions let you allow, deny, or require approval before a tool runs, with read-only and write/delete tools grouped so you can set them in bulk.

This is separate from QA.tech's own MCP server for AI coding tools, which now lives under Organization Settings → MCP Server.
# Direct link
Highlight
Featured this release
Agent tests can now verify network requests
Instruct the agent to check that a specific network request fired – URL, method, status and bodies.
Write a step like "verify network request to /api/orders with status 200" and the agent checks the request's URL, method, status code, and request/response bodies as part of the test. If nothing matches exactly, it reports the closest near-miss so you can see what actually fired.

Matched checks appear in the action log as a "Verify Network Request" step, building on the network visibility added earlier this month.
# Direct link
Update 03 of 04
Agents can now draw circles and custom shapes
The testing agent traces circles, blobs and polygons in one continuous stroke instead of only straight-line drags.
Tests that involve a canvas, signature pad or map drawing tool no longer have to be expressed as straight-line drags. The web testing agent can trace curved or straight-edged shapes – circles, blobs, rectangles, polygons – in a single continuous stroke, closing the shape when the tool expects it.
# Direct link
Update 04 of 04
Change a test case's agent from chat
Ask chat to move a test to a different agent – the same switch that used to require the UI.
Tell chat to switch a test to your mobile or desktop agent and it applies immediately, matching what the quick-edit menu already does. Chat checks the agent against the test's application type first, so an incompatible pairing returns a clear error instead of silently reverting at run time.
# Direct link

Connect your team's MCP tools to the AI chat

Agent tests can now verify network requests

Agents can now draw circles and custom shapes

Change a test case's agent from chat

Your team moves fast. Can your testing keep up?