v2.0.1

TestDino MCP v2.0.1

New package name: this release publishes as @testdino/mcp. If you were on the old testdino-mcp package, update your MCP config to @testdino/mcp (for example "args": ["-y", "@testdino/mcp"]). Same tools and behavior, new name.

TestDino MCP is no longer just about managing and analysing your tests. It now acts on them. From a failed test you can file a tracked bug in your issue tracker, cut through a big red run by grouping failures into real problems, and dig into test history with far more precision. All from natural language, right inside Cursor, Claude Code, or VS Code.

Turn failing tests into tracked issues, without leaving your editor

Connect your team's issue tracker once, then ask your AI assistant to file a ticket straight from a failed test or run. Supported trackers:

• Jira
• Linear
• Asana
• monday.com

What you can now do:

• Connect a tracker by asking your assistant to link the integration (it hands you a secure authorization link to approve in your browser).
• File an issue from a failure with the test context already attached, so the ticket lands with the right details instead of a blank template.
• Check issue status later by asking for updates on tickets you have already filed, including their current state in the external tool. Ask about several at once.
• See what's connected for a project before you start, so you always know which trackers are live.

The result: the gap between "a test failed" and "a ticket exists for it" is now one sentence.

Triage big failing runs by pattern, not one test at a time

When a run fails with dozens of red tests, you no longer have to read them one by one. Ask your assistant to cluster the failures and it groups tests that share the same underlying error. You immediately see which failures are one real problem versus many, so you can fix the root cause first and stop chasing duplicates.

Sharper filtering and history for test runs and cases

Finding the exact run or test you care about is faster now:

• Filter runs by status, by test case tags, by free-text search, and sort the results, so you can zero in on the runs that matter instead of scrolling.
• Filter for artifacts to find tests that actually have screenshots, videos, or traces available, including artifacts from earlier attempts of a flaky test.
• Pull test history and step detail for a case, so you can see how a test has behaved over time and what happened at each step.

Know your access at a glance

The health check now shows your role in the organization, so you can confirm what you are able to do before you try it.

New tools in this release

Five new capabilities your AI assistant can now call:

• connect_integration — link an issue tracker (Jira, Linear, Asana, monday.com) to a project.
• get_integration_status — check which trackers are connected before you act.
• create_external_issue — file a ticket from a failing test or run.
• get_external_issue — pull the current status of tickets you have filed.
• get_run_error_clusters — group a run's failures by their underlying error to triage at scale.

Notes for existing users

A few things changed that need a one-time update:

• New package name. Point your MCP config at @testdino/mcp instead of testdino-mcp. The old package is no longer updated.
• Create a new PAT. Generate a fresh Personal Access Token in TestDino and use it in your MCP config. Tokens from earlier versions will not work with this release.
• New service address. The MCP now talks to mcp.testdino.com. If you set a custom API URL in your config, update it. If you use the default, there is nothing to do.

Switch your config to @testdino/mcp, swap in your new PAT, and you are set.