TLDR
A quick start to your first AI-powered test with Thunders MCP: connect your AI, author, execute, and analyze tests: all without code.
Let your AI assistants author, execute, and reason on tests. Thunders MCP connects tools like Claude, ChatGPT, Cursor, Devin, or Windsurf directly to your testing environments, workflows, and results. Turn plain English commands into fully automated tests: no scripts, no setup, no context switching. Just ask your favorite AI, it does the rest.
Example Commands (micro-copy under sub-headline):
→ “Convert this Selenium test suite into executable Thunders test cases.”
→ “Investigate why this test failed and suggest possible fixes.”
→ “Pull in the most recent test set run and highlight any critical failures.”
→ “Build a new test case from this Figma design and add it to the smoke test set.”
How to Install Thunders MCP
Get Connected in 2 Minutes
Thunders MCP works with any MCP-compatible AI client, including:
- Claude Desktop
- ChatGPT Desktop
- Cursor
- Devin
- Windsurf
No SDKs. No coding. Just connect and go.
3 Simple Steps:
- Add the Server
- Open MCP settings in your AI client
- Add Server URL:
https://api.thunders.ai/v1/mcp
- Authorize Securely
- OAuth login via Thunders
- Tokens stored automatically, passwords never shared
- Test Your Connection
Ask Thunders to prove it’s connected
“Knock Knock, is Thunders connection set?"

If results appear, you’re ready ✅
Use cases/ What You can Ask:
Turn Any Prompt Into Automated QA
Examples of what your AI can do via Thunders MCP:
1. Convert legacy tests
Migrate Playwright, Selenium, or Cypress test suites into executable Thunders test cases, without manual rewriting.
2. Author tests from context
Build test cases from flows, requirements, or Figma designs and organize them into test sets.
3. Run tests with personas
Execute tests using different personas, such as QA Engineer or Accessibility Tester, depending on what you want to validate.
4. Run tests with control
Trigger test runs on specific environments and review results in Thunders.
5. Understand results and trends
Review failures, coverage gaps, and recurring issues across recent test runs.








