Thunders comes with a bunch of integrations ready to go out of the box. Nonetheless, if there's an MCP server out there that isn't on our built-in list, you can now connect it yourself. Any MCP server you have access to can become a connector in Thunders.
This is handy if your team runs an internal MCP server, or if you want to plug in a niche tool that we haven't added natively yet.
Two ways to get there
Both paths lead to the same place, so pick whichever is closer at hand.
From the Thunders AI tab:
Open the Thunders AI tab, click + in the message box, then click Connectors.
Point to Add connector.
Click Custom connector.
From the Connectors page:
Filling in the details
Once you're in the Custom connector dialog, you'll need three things:
Display name: whatever helps you recognize it later, e.g.
Custom MCP.Server URL: the address of your MCP server, e.g.
https://mcp.example.com/mcp.Authentication: choose Sign in (OAuth) or API token, depending on what your server expects.
Hit Add connector, and that's it: your custom MCP server is live.
Your connector is now in your connectors list, ready to use in Thunders.
Use your custom connector for bug reports
A custom connector can receive bug reports from a failed step, like the built-in connectors.
Click Configure, then Connectors.
On the row of your custom connector, click Manage.
Check that Use for bug reports is selected. It is on by default, and Thunders saves a change at once.
Optional: in Guidance, write instructions for Thunders AI, for example the project or the labels of new tickets. Click Save. The Guidance field shows only while Use for bug reports is selected.
When you report a bug from a failed step, your connector shows in the Tool list under its display name. For the other steps, see how to report a bug from a failed run.
Clear Use for bug reports to keep the connector out of the Tool list. Thunders AI can still use the tools of the connector in chat.
To sign in to the server again, open the ⋮ menu on the row of your connector and click Reconnect. This applies to a connector that you added with Sign in (OAuth). For a connector that you added with an API token, Reconnect does not work. Click Disconnect, then add the connector again with the new token.





