testdino-mcp

Testdino MCP Server

TestDino test results and manual testing workflows become accessible through AI clients such as Cursor and Claude Desktop. QA teams and developers can investigate failures, maintain test cases, organize suites, and coordinate runs through conversation.

Server facts

testdino-mcp

Tech

Runtime / language
node
Transports
stdio
Remote available
No
Authentication
Not specified

Activity

GitHub stars
9
Last commit
Data as of

Tags

  • Debugging
  • Playwright
  • ci cd
  • reporting
  • test management
  • testing

Overview

TestDino’s execution history gives developers and QA teams a starting point for investigating failed tests through an AI assistant. Users can narrow runs by branch, author, environment, commit, or time, then inspect individual cases for errors, stack traces, logs, execution steps, and available screenshots, videos, or traces. Historical debugging data helps the client compare executions and examine recurring failures. A connection check validates the configured personal access token and identifies accessible organizations and projects before users explore their test data.

Manual testing workflows cover finding, creating, and revising cases with steps, conditions, priorities, and other metadata, plus arranging them in nested suites. The README also describes release planning, scoped manual runs, tester assignments, per-case results, and exploratory sessions with a mission or charter. These workflows let teams connect test execution to release tracking within the same conversational interface. For code-focused reviews, the documented audit workflow combines a supplied prompt with branch context, analyzes source locally, and sends the resulting report to TestDino without uploading raw source files.

testdino-mcp setup notes

  • testdino-mcp records stdio only; confirm a network transport upstream before planning remote access.

Related MCP servers