TestDino MCP
JSON →A Model Context Protocol (MCP) server that connects TestDino to AI agents. This server enables you to interact with your TestDino test data directly through natural language commands.
Install
npx (Recommended Tools · 27
- health Verify your connection and validate your PAT. Shows account information, available organizations, and projects with access permissions.
- list_testruns Browse test runs with powerful filters (branch, time interval, author, commit, environment). Supports pagination and batch operations.
- get_run_details Get comprehensive details about a specific test run including statistics, test suites, test cases, and metadata. Supports batch operations (comma-separated IDs, max 20).
- list_testcase List test cases with comprehensive filtering (by test run, status, browser, error category, branch, environment, commit, author, spec file, tags, runtime, artifacts, and more). Can filter by test run criteria or directly by test case properties.
- get_testcase_details Get detailed information about a specific test case including error messages, stack traces, test steps, console logs, and artifacts. Can identify by testcase_id alone or by testcase_name with testrun_id/counter.
- debug_testcase Debug a test case by aggregating historical failure data across multiple executions. Returns failure patterns, error categories, common error messages, error locations, browser-specific issues, and a pre-formatted debugging prompt for AI analysis. Perfect for root-cause analysis and identifying flaky test behavior.
- test_audit Run a single-pass test quality audit. Fetch the server-curated prompt and branch signals, analyze the repo locally, submit the completed report, browse historical audit reports, and optionally save TEST-AUDIT.md locally.
- list_manual_test_cases Search and list manual test cases with comprehensive filtering (project, suite, status, priority, severity, type, layer, behavior, automation status, tags, flaky status).
- get_manual_test_case Get detailed information about a specific manual test case including steps, custom fields, preconditions, postconditions, and all metadata.
- create_manual_test_case Create new manual test cases with steps, preconditions, postconditions, and metadata (priority, severity, type, layer, behavior).
- update_manual_test_case Update existing manual test cases (title, description, steps, status, priority, severity, type, layer, behavior, preconditions, postconditions).
- list_manual_test_suites List test suite hierarchy to find suite IDs for organization. Supports filtering by parent suite.
- create_manual_test_suite Create new test suite folders to organize test cases. Supports nested suites by providing parentSuiteId.
- list_releases Browse releases for a project with filters (search, type, completion status, parent release). Releases group runs + sessions and can nest up to 3 levels deep.
- get_release Get full details for one release including dates, status, parent/root hierarchy, and rolled-up progress stats across all runs in this release and its descendants. Accepts internal _id or counter-style ID like MS-12.
- create_release Create a new release with name, type, dates, and optional parent for nesting.
- update_release Modify an existing release — name, dates, completion flags, type, linked issues. Closed releases are still editable.
- list_manual_runs Browse manual runs in a project. Filter by status, state, environment, release, tags, or free-text name search.
- get_manual_run Get full details for one run — test stats (total/passed/failed/blocked/untested), contributors, attachments, linked release. Accepts internal _id or counter-style ID like RUN-12.
- create_manual_run Create a new manual run. Choose selectionMode='all' for every case in the project, or 'selected' with suite/case IDs to scope it. Attach to a release with releaseId.
- update_manual_run Modify run metadata — name, environment, state, release attachment, tags. Closed runs are read-only except for releaseId.
- list_run_test_cases Get the per-case execution rows inside a run — exactly what the UI shows in the run's test-case table. Each row includes the current assignee and current result. Filter by assignee (email or _id) or result.
- update_run_test_case Set the assignee and/or result for one test case inside a run — same as clicking 'Assign to' + the result pill in the UI. Works even on untested cases (auto-creates the per-case row on first edit). Accepts caseKey (TC-156), test case _id, or the internal tcm_rtc_… ID.
- list_sessions Browse exploratory sessions in a project. Filter by status, state, sessionType, assignee (email or _id), release, tags.
- get_session Get full details for one session — name, mission, status, assignee, linked release, findings. Accepts internal _id or counter-style ID like SES-12.
- create_session Create a new exploratory session with mission/charter, sessionType, assignee, estimate, and optional release attachment.
- update_session Modify session metadata — name, mission, assignee, state, estimate, linked issues, attachments.
Links
★ 7 GitHub stars