Testdino MCP server

by testdino-inc·io.github.testdino-inc/testdino-mcp·v1.0.2·9 stars

No reviews yet

A MCP server for TestDino

A85/100grade A

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

A85/100

full report

Adoption

Growing

9 stars980 downloads/wk

Reviews

Write one

Nobody has reviewed Testdino yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Testdino tools (6, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

get_run_detailswrite action
Get detailed information about test runs. Shows test statistics (passed, failed, skipped, flaky), all test suites and cases, git metadata, and error details. Supports batch operations (comma-separated IDs, max 20). Use this to analyze test execution health or debug specific failures.
get_testcase_details
Get detailed information about a specific test case. You can identify the test case in two ways: 1) By testcase_id (can be used alone), or 2) By testcase_name combined with testrun_id or counter (required because test cases can have the same name across different test runs). Shows error messages, stack traces, test steps, console logs, and optional artifacts (screenshots, videos, traces). Use this
health
Check if your TestDino connection is working. Verifies your API key and shows your project name. Use this first to make sure everything is set up correctly.
list_testcase
List test cases with comprehensive filtering options. You can filter by test run (ID or counter), status, spec file, error category, browser, tags, runtime, artifacts, error messages, attempt number, branch, time interval, environment, author, or commit hash. When using test run filters (by_branch, by_commit, by_author, by_environment, by_time_interval, by_pages, page, limit, get_all), the tool fi
list_testruns
Browse and filter your test runs to find specific test executions. Filter by git branch (e.g., 'develop', 'main'), time interval ('1d', '3d', 'weekly', 'monthly', or custom date ranges), commit author, or environment (e.g., 'production', 'staging', 'development'). Supports efficient pagination using page/limit or offset/limit, or use get_all=true to fetch all results (up to 1000). Returns test run
upload_latest_local_test_runswrite action
Upload your local Playwright test results to TestDino. After running tests locally, upload the report to track and analyze results. Automatically detects git info (branch, commit, author). Use absolute paths for best results.

Public scan report

scanner v0.1.10 · 2026-10-01 · same rubric, same numbers if you re-run it

no findings

Code scan25 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitystatic API keys via environment variables6/15
Maintenancelast push 15 days ago15/15
Maintainer identityregistry namespace matches repository owner; GitHub account older than a year9/10

Overall 85/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Testdino compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 85/100; higher than 70% of 48,255 servers
Tools: 6; the typical server has 7
Tools that change things: 33%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 9; more than 87% of 28,688 servers
Downloads a week: 980; more than 95% of 12,191 servers with a package

What its tools let an agent do: 4 read · 1 create · 1 change

Install Testdino in Claude Code, Cursor or VS Code

Runs npx -y testdino-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add testdino-mcp -- npx -y testdino-mcp

Add to Cursor

What the publisher says

From the Testdino repository's README, as published. We do not edit it. Read it on GitHub

TestDino MCP

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.

Quick Start

Add this to your MCP client config (~/.cursor/mcp.json for Cursor), then restart the client:

{
  "mcpServers": {
    "TestDino": {
      "command": "npx",
      "args": ["-y", "@testdino/mcp"],
      "env": {
        "TESTDINO_PAT": "your-pat-here"
      }
    }
  }
}

Get your PAT from TestDino → User Settings → Personal Access Tokens, then ask your assistant: "Check TestDino health." You should see your account, organizations, and projects. Full setup for Cursor and Claude Desktop is in Integration.

What is This?

This MCP server bridges the gap between your TestDino test management platform and AI agents. Instead of manually navigating the TestDino dashboard, you can ask your AI assistant to:

Check test run results
Analyze test failures
Get detailed test case information
Manage manual test cases and suites
Plan releases, spin up manual test runs, and assign testers
Run exploratory testing sessions
Record per-case verdicts (passed / failed / blocked / etc.) from chat

All through simple conversational commands.

Features

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Testdino: common questions

Is Testdino MCP server safe?: Yes, by our scan: it is graded A (85/100). Read the Testdino safety report
How do I install Testdino?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Testdino need an API key?: Yes. The registry entry asks for YOUR_API_KEY.
Is Testdino maintained?: The last commit was 48 days ago (2026-09-17). The latest release is v1.0.2.
How does Testdino compare with other MCP servers?: safety score 85/100 (higher than 70% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 33% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.