How to Use the TestDino Plugin for Testing in Claude Code

The TestDino plugin integrates Claude Code with the TestDino MCP server, allowing you to query test runs, manage manual tests, and audit flaky tests using natural language commands that translate directly to REST API calls.

The TestDino plugin bridges Claude Code with the TestDino Model-Centric Platform (MCP), enabling developers to interact with test infrastructure without leaving their development environment. By connecting to the remote MCP endpoint at mcp.testdino.com, this plugin transforms conversational requests into structured API queries against your test data. Whether you need to inspect recent test executions or author new manual test cases, the plugin streamlines quality assurance workflows within the anthropics/claude-plugins-community ecosystem.

Installation and Configuration

To begin using the TestDino plugin for testing in Claude Code, you must first install it from the Claude marketplace and verify the MCP endpoint configuration.

Adding the Plugin from the Marketplace

The plugin is distributed through the testdino-hq/TestDino-Plugins repository. Install it using the following Claude Code commands:

/plugin marketplace add testdino-hq/TestDino-Plugins
/plugin install testdino@testdino-plugins

These commands register the plugin with your Claude Code environment according to the metadata defined in testdino/.claude-plugin/plugin.json and testdino/.claude-plugin/marketplace.json.

MCP Endpoint Configuration

The plugin communicates with TestDino's infrastructure via HTTPS through the MCP server. The configuration is stored in testdino/.mcp.json, which specifies:

{
  "url": "https://mcp.testdino.com"
}

This endpoint handles all test data queries and management operations. The connection is stateless; the plugin forwards Claude-generated prompts to the MCP REST API without maintaining persistent session state beyond the current request.

Querying Test Runs

Once installed, you can retrieve test execution data using natural language. The skill definition in testdino/skills/testdino-runs/SKILL.md enables Claude to parse requests for test run information and translate them into API calls.

To fetch recent test executions, prompt Claude:

Show me the last five test runs for the `checkout` suite.

Claude Code translates this into a GET request to https://mcp.testdino.com/runs?limit=5&suite=checkout and returns a formatted table containing run IDs, execution status, and timestamps. This eliminates the need to manually construct HTTP requests or navigate external dashboards.

Managing Manual Tests

The plugin supports creating and organizing manual test cases through conversational interfaces. The skill configuration in testdino/skills/testdino-manual-tests/SKILL.md defines how Claude structures manual test creation payloads.

To create a new manual test entry:

Create a manual test called 'Verify cart total' with steps to add items and check the total.

Claude Code issues a POST request to https://mcp.testdino.com/manual-tests with the structured payload containing the test name and step definitions. The plugin confirms creation by displaying the assigned test ID and verification link from the API response.

Auditing Flaky Tests

For quality assurance analysis, the plugin provides access to TestDino's audit capabilities through the endpoint defined in testdino/skills/testdino-audit/SKILL.md. This feature identifies unstable tests and suggests remediation strategies.

To analyze test reliability:

Find flaky tests in the last week and suggest fixes.

Claude Code calls the /audit endpoint, retrieves a list of flaky test identifiers, and generates contextual remediation suggestions based on the returned failure patterns and historical stability metrics.

Plugin Architecture and Key Files

Understanding the plugin structure helps with troubleshooting and advanced configuration. The TestDino plugin follows the standard Claude plugin layout within the anthropics/claude-plugins-community repository:

• testdino/.claude-plugin/plugin.json - Declares the plugin name, homepage URL, and repository location
• testdino/.claude-plugin/marketplace.json - Registers the plugin in the Claude marketplace index
• testdino/.mcp.json - Stores the MCP server configuration and endpoint URL
• testdino/README.md - Contains installation instructions and usage badges
• testdino/skills/testdino-runs/SKILL.md - Defines the test run query skill parameters
• testdino/skills/testdino-manual-tests/SKILL.md - Specifies the manual test creation schema
• testdino/skills/testdino-audit/SKILL.md - Configures the flaky test audit parameters

All interactions require no additional credentials beyond the default public MCP endpoint, as authentication is handled transparently through the plugin's HTTPS connection to mcp.testdino.com.

Summary

• The TestDino plugin connects Claude Code to the TestDino MCP server at https://mcp.testdino.com for seamless test management
• Install the plugin using /plugin marketplace add and /plugin install commands referencing testdino-hq/TestDino-Plugins
• Query test runs, create manual tests, and audit flaky tests using natural language that the plugin translates to REST API calls
• Configuration files including testdino/.mcp.json and testdino/.claude-plugin/plugin.json define the plugin behavior and MCP endpoint
• All test data interactions are stateless HTTPS requests requiring no manual credential management

Frequently Asked Questions

How do I install the TestDino plugin in Claude Code?

Add the plugin from the marketplace using /plugin marketplace add testdino-hq/TestDino-Plugins, then run /plugin install testdino@testdino-plugins to activate it. These commands reference the metadata defined in testdino/.claude-plugin/plugin.json to register the plugin with your Claude Code session.

What MCP endpoint does the TestDino plugin use?

The plugin communicates with https://mcp.testdino.com as specified in testdino/.mcp.json. This endpoint handles all test run queries, manual test creation, and audit operations via stateless REST API calls.

Can I use the TestDino plugin without additional authentication credentials?

Yes. The plugin operates through the default public MCP endpoint using HTTPS connections. No manual API key configuration or credential setup is required beyond the standard Claude Code installation process, as the plugin manages authentication transparently.

What types of testing operations does the TestDino plugin support?

The plugin supports three primary operations defined in the skills directory. These include querying historical test runs via testdino/skills/testdino-runs/SKILL.md, creating manual test cases via testdino/skills/testdino-manual-tests/SKILL.md, and auditing flaky tests via testdino/skills/testdino-audit/SKILL.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}