Connect external tools so Thunders AI can use them as knowledge sources when creating tests, and as destinations for bug reports.
Connectors are managed from the Connectors page in your project navigation. Each connector can serve one or both roles:
Knowledge source: Thunders AI reads tickets, specs, pages, or tests from the tool and uses them as context when creating or editing test cases.
Bug reporting: Thunders AI files bug tickets in the tool from failed runs, with the failure context included (test case, run, failed step, expected result, and actual result).
Available connectors
Connector | Use as |
Atlassian Cloud (Jira and Confluence) | Knowledge source and bug reporting |
Jira Data Center | Knowledge source and bug reporting |
Confluence Data Center | Knowledge source |
Xray for Jira | Knowledge source |
Xray Data Center | Knowledge source |
Linear | Knowledge source and bug reporting |
Notion | Knowledge source and bug reporting |
ClickUp | Knowledge source and bug reporting |
Shortcut | Knowledge source and bug reporting |
Azure DevOps | Knowledge source and bug reporting |
Web Browse is built in and always available. It is not a connector: enable it from the source selector whenever you want Thunders AI to visit a live URL.
For the full Xray setup guide (Cloud and Data Center), see Xray Integration: Import Tests, Create & Sync Results.
Connect a tool
Open Connectors from your project navigation.
Search for the tool, or filter the list by Knowledge Source or Bug Reporting.
Click Connect and follow the steps for that tool.
Add a custom connector
If the tool you need is not in the list, you can add a custom connector (an external MCP server). Click Add on the Connectors page.
Enabling connectors per conversation
After a tool is connected, enable or disable it for each conversation using the source selector at the bottom of the Thunders AI input. Only enabled connectors are used for that conversation.
Example
You: Create a test case from KAN-28 in Jira
Thunders AI will look up the Jira ticket, read its acceptance criteria, and use that as context to generate the test case.
