QA.tech + Custom MCP Integrations
Custom MCP is the reverse direction of the MCP server: the QA.tech chat agent uses tools from services you connect via a remote MCP server, authenticated with OAuth, a bearer token, or no auth. Every tool gets a permission level: allow, needs approval, or blocked. For TestRail and Xray, use the built-in integrations instead; Custom MCP is for everything else.
What you can do
- Let the agent look up records in a homegrown ticketing or test-management system
- File records in external systems directly from chat
- Gate risky tools behind per-call approval
Set it up
Connecting Custom MCP Integrations
- 01
Add your remote MCP server URL in QA.tech's Integrations settings.
- 02
Pick the auth method: OAuth, bearer token, or none.
- 03
Set a permission level per tool: allow, needs approval, or blocked.
Full reference in the QA.tech docs.
Where teams use this
Custom MCP Integrations in practice
This is how the agent reaches systems we haven't built a native integration for. Teams connect internal admin panels and homegrown trackers so test generation can pull real data, and CRM-heavy workflows can ground tests in records from the actual system.
FAQ
Common questions
- When should I use Custom MCP vs a built-in integration?
- Built-in wins whenever it exists (Jira, Linear, TestRail, Xray, and the rest of this directory). Custom MCP covers everything else.
- Can I restrict what the agent may call?
- Yes, per tool: allow, needs approval, or blocked.
Related integrations
MCP Server
Next →Vercel Preview Protection
Your team moves fast. Can your testing keep up?
QA.tech agents test your product autonomously, so moving fast never means shipping broken. See how it works in a 30-minute demo.