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.”
Thunders MCP works with any MCP-compatible AI client, including:
No SDKs. No coding. Just connect and go.
https://api.thunders.ai/v1/mcpAsk Thunders to prove it’s connected
“Knock Knock, is Thunders connection set?"
If results appear, you’re ready ✅
Examples of what your AI can do via Thunders MCP:
Migrate Playwright, Selenium, or Cypress test suites into executable Thunders test cases, without manual rewriting.
Build test cases from flows, requirements, or Figma designs and organize them into test sets.
Execute tests using different personas, such as QA Engineer or Accessibility Tester, depending on what you want to validate.
Trigger test runs on specific environments and review results in Thunders.
Review failures, coverage gaps, and recurring issues across recent test runs.
Traditional QA
Thunders MCP
Where testing
happens
Inside a dedicated testing tool
Directly from AI tools where work happens
Who operates
tests
Humans (QA, engineers)
AI assistants operating the testing system
Test
creation
Manually written or scripted
Authored from intent, context, or legacy tests
Legacy test
migration
Manual rewrite or partial reuse
Automatic conversion from Selenium, Playwright, or Cypress
Execution
control
Triggered from UI or CI only
Triggered from AI tools with full environment context
Personas
& intent
Implicit, human-driven
Explicit personas (QA Engineer, Accessibility Tester, etc.)
Failure
analysis
Manual inspection of logs and reports
Explained in natural language with steps, and logs
Context
switching
Frequent (PM → QA tool → CI → tracker)
None. Author, run, and analyze in one place
Whether you're getting started or scaling advanced workflows, here are the answers to the most common questions we hear from QA, DevOps, and product teams.
Thunders MCP (Model Context Protocol) securely connects AI assistants to your Thunders workspace so they can generate, manage, and execute tests for you.
No. Everything works through natural language prompts.
Yes. OAuth authentication, encrypted tokens, automatic refresh, and revocable access.
Claude Desktop, ChatGPT Desktop, Cursor, Devin, and Windsurf. More integrations will be added as MCP adoption grows.
Only what’s necessary: read projects, tests, environments, and personas; create, modify, and execute tests.
Yes, MCP works with any dev or staging endpoints for testing or experimentation.
Revoke access anytime from your AI or Thunders account settings.
