Testdino Plugins

Name: Testdino Plugins
Author: TestDino

testdino-hq/TestDino-Plugins·1 plugin

Plug TestDino into Claude Code via hosted remote MCP to inspect runs, debug failures, manage manual tests, and run audits without leaving the agent.

Overview

testdino-plugins is a plugin marketplace for the Ship phase that connects Claude Code to TestDino through a remote MCP server for runs, debugging, manual tests, and audits.

What is this marketplace?

Hosted remote MCP server integration for TestDino inside Claude Code
Inspect automated test runs and debug failing cases from the agent
Manage manual tests alongside automation from one platform bridge
Run TestDino audits through the same MCP connection
Playwright and QA-oriented keywords in the official plugin manifest
Marketplace bundle contains 1 plugin (testdino) at version 1.0.0
MIT license with homepage testdino.com
Integration is explicitly a hosted remote MCP server, not a local-only shim

Compatible agents: Claude Code, Cursor, any compatible agent

What problem does it solve?

You lose hours bouncing between Playwright failures, spreadsheets for manual cases, and separate audit tools while Claude Code sits disconnected from your test hub.

Who is it for?

Solo builders and small teams already on TestDino who want agent-driven QA inspection during ship week.

Skip if: Developers who only run `npm test` locally with no test management platform and no appetite for another SaaS login.

What do I get? / Deliverables

After install, your agent can inspect TestDino runs, debug failures, manage manual tests, and execute audits via the hosted MCP bridge.

Connected TestDino MCP session from Claude Code
Agent-accessible test run inspection and failure debugging
Ability to manage manual tests and trigger TestDino audits via MCP

Plugins in this marketplace

1 plugin — install individually after you add the marketplace.

PluginVersion

TestdinoUse TestDino inside Claude Code through the hosted remote MCP server to inspect test runs, debug failing test cases, manage manual tests, and run TestDino audits.1.0.0

Recommended Marketplaces

Anti Halltalas9/anti-hall

anti-hall is a Claude Code plugin marketplace centered on a single verify-first discipline plugin for solo builders who …1 stars

Bee Reviewheresun/SuperReview

bee-review (SuperReview marketplace) is an AI swarm code review plugin for Claude Code, maintained by 焦点科技 / David under…

Bug EchoTerryc21/bug-echo

bug-echo is a Claude Code marketplace plugin by Terry Nyberg that extends debugging beyond the line you just patched. Wh…

Chrome Test Runner Marketplacevictor-qin/chrome-test-runner-plugin

chrome-test-runner-marketplace delivers one chrome-test-runner plugin (0.2.0) for solo builders who ship web apps and ne…

Claude Harnessess-hiraoku/claude-harnesses

claude-harnesses is a ten-plugin Claude Code marketplace from s-hiraoku that packages opinionated shipping harnesses for…

Claude In MobileAlexGladkov/claude-in-mobile

claude-in-mobile is an AlexGladkov Claude marketplace entry that publishes one plugin described as a mobile device autom…286 stars

Journey fit

Primary fit

Test management and Playwright-oriented debugging sit in Ship when you are hardening quality before release. The plugin is explicitly for test runs, QA workflows, and audits—not launch distribution or production monitoring.

How it compares

Hosted QA MCP marketplace, not on-device codebase memory like Tessera or Telegram messaging.

Common Questions / FAQ

Who is Testdino Plugins for?

Builders using Claude Code who centralize testing in TestDino and want MCP-driven run inspection and audits.

When should I use Testdino Plugins?

Use it in Ship testing when you need to debug failures, coordinate manual cases, and run audits before release.

How do I add Testdino Plugins to my agent?

Add the testdino-hq/TestDino-Plugins marketplace in Claude Code, install the testdino plugin, and authenticate against the hosted remote MCP per TestDino docs.