The assistant says it has no Thunders tools
Run through these in order:
Check the URL: It is
https://api.thunders.ai/v1/mcp, withapi, notapp. A wrong host is the single most common cause.Check you authorized: Adding the server and signing in are two separate steps. Look for a Connect, Needs login or Authorize action next to Thunders in your client's settings.
Enable it for the conversation: ChatGPT and some other clients require you to switch the connector on per chat.
Restart the client: Cursor and VS Code sometimes need a reload before newly added tools appear.
Authorization fails or loops back to sign-in
Make sure you are signing in to the Thunders account that actually has access to your projects. If you belong to more than one organization, sign out of Thunders in that browser first and start the flow again.
Disable strict tracking protection, or try a normal window instead of a private one. The OAuth redirect needs cookies.
The connector was working and now returns errors
The authorization was probably revoked, or you changed Thunders accounts. Disconnect Thunders in your client and connect it again.
I cannot find the setting to add a custom connector
In Claude, custom connectors require a paid plan (Pro, Max, Team or Enterprise). They are not available on the free plan.
In ChatGPT, developer mode is available on free and paid plans, so a plan is rarely the cause. On Business, Enterprise and Education accounts a workspace admin can turn developer mode off or restrict which connections are allowed, so check with your admin.
The assistant cannot find my project or test case
Ask it to list first: "List all my Thunders projects." Names are matched from what the tools return, so if the project is missing from that list, it is a permissions question rather than an MCP one. Check that your Thunders account has access to it.
Answers are slow, or the assistant looks at the wrong project
Name the project up front: "In the Checkout project...". Without it, the assistant may pull test cases across every project you can access before narrowing down.
A run was queued that I did not want
Queuing is a destructive action, so your client should have asked first. If it did not, check whether you granted "always allow" to that tool earlier in the session, and reset the permission in your client's settings.
A test case was deleted that I did not want deleted
Deleting is a destructive action and your client should have asked first. As above, check whether "always allow" was granted to that tool earlier in the session and reset it in your client's settings.
FAQ
Do I need an API token?
No. The MCP server uses OAuth in the browser. API tokens are for the REST API and CI/CD, not for MCP.
Which clients are supported?
Any client that supports remote MCP servers over HTTP with OAuth, including Claude, ChatGPT, Cursor, VS Code, Windsurf and Devin. See Connect another AI client to Thunders MCP.
Do test runs started over MCP consume credits?
Yes. A run queued by an assistant is an ordinary test run and is billed the same way.
Can my teammates share one connection?
No, and they should not. Each person authorizes with their own Thunders account, so permissions and audit history stay accurate. Config files can be shared, credentials cannot.