MCP Server By TestMu AI

Generate HyperExecute YAML

generateHyperExecuteYAML

Read-only

Generates a HyperExecute YAML configuration for running tests on TestMu AI's HyperExecute platform.

REQUIRED fields: project (language, framework) and testing (testDiscovery.command, testRunnerCommand) All other fields are OPTIONAL.

Supports multiple languages and frameworks:

JavaScript/TypeScript: Playwright, Cypress, WebDriverIO, Puppeteer, Taiko
Python: Pytest, Behave, Robot Framework
Java: TestNG, JUnit, Cucumber
Ruby: RSpec, Capybara
C#: NUnit, xUnit, MSTest
Mobile (ONLY use appTesting for these): XCUI (iOS), Espresso (Android), Appium

Features:

Smart framework defaults for common configurations
Input validation with security checks
Caching and artifact upload configuration
Git integration via sourcePayload
Mobile app testing support (via optional appTesting field)

The appTesting field applies to mobile app testing only; web automation (Selenium, Playwright, Cypress, etc.) leaves it out.

Tool call template

Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.

{
  "id": 1,
  "jsonrpc": "2.0",
  "method": "tools/call",
  "params": {
    "arguments": {
      "project": "<project>",
      "testing": "<testing>"
    },
    "name": "generateHyperExecuteYAML"
  }
}

Input Schema

Name	Required	Description
`setup`	No	Setup configuration (optional)
`project`	Yes	Project configuration
`testing`	Yes	Test configuration
`advanced`	No	Advanced overrides (escape hatch for any HyperExecute field)
`jobLabel`	No	Labels for the job
`artifacts`	No	Artifact configuration (optional)
`execution`	No	Execution settings (optional)
`appTesting`	No	Mobile app testing configuration (XCUI, Espresso or Appium). Web automation (Selenium, Playwright, Cypress, etc.) leaves it out.
`sourcePayload`	No	Git integration: fetches the test code from a remote Git repository. Only needed when the code is not already present locally; local code (the usual case) leaves it out.

Schema Changelog

Changes observed during successful MCP inspections.

Changed20 schema fields changedOct 9, 2026

changedInput schema / properties / appTesting / description

Previous value: -"Mobile app testing configuration. ONLY for mobile testing (XCUI/Espresso/Appium). DO NOT include this for web automation tests (Selenium, Playwright, Cypress, etc.)."New value: +"Mobile app testing configuration (XCUI, Espresso or Appium). Web automation (Selenium, Playwright, Cypress, etc.) leaves it out."

addedInput schema / properties / appTesting / properties / deviceLog / description
```
Added value: +"Capture device logs"
```
addedInput schema / properties / appTesting / properties / networkLog / description
```
Added value: +"Capture network logs"
```
addedInput schema / properties / appTesting / properties / video / description
```
Added value: +"Record a video of each test"
```
addedInput schema / properties / artifacts / properties / mergeArtifacts / description
```
Added value: +"Merge the artifacts from all parallel runners into one set"
```

addedInput schema / properties / artifacts / properties / uploadPaths / description

Added value: +"Paths on the runner to upload as job artifacts, e.g. reports/ or screenshots/"

addedInput schema / properties / execution / properties / autosplit / description

Added value: +"Spread the discovered tests across the parallel runners automatically"

addedInput schema / properties / execution / properties / concurrency / description
```
Added value: +"Number of tests run in parallel"
```
addedInput schema / properties / execution / properties / maxRetries / description
```
Added value: +"Retries per failed test when retryOnFailure is on"
```
addedInput schema / properties / execution / properties / os / description
```
Added value: +"Runner operating system"
```
addedInput schema / properties / execution / properties / retryOnFailure / description
```
Added value: +"Retry failed tests"
```
addedInput schema / properties / setup / properties / runtime / properties / language / description
```
Added value: +"Runtime to install on the runner, e.g. node, python, java"
```
addedInput schema / properties / setup / properties / runtime / properties / version / description
```
Added value: +"Runtime version, e.g. 20 or 3.11"
```

changedInput schema / properties / sourcePayload / description

Previous value: -"Git integration - ONLY include this if the user explicitly requests fetching code from a remote Git repository. Do NOT include this when code is already present locally (which is the default case). Most users run tests on local code and do not need sourcePayload."New value: +"Git integration: fetches the test code from a remote Git repository. Only needed when the code is not already present locally; local code (the usual case) leaves it out."

changedInput schema / properties / sourcePayload / properties / accessToken / description

Previous value: -"Use env var reference: ${GIT_TOKEN}"New value: +"Reference to an environment variable that holds the Git token, e.g. ${GIT_TOKEN}; never the token itself"

addedInput schema / properties / sourcePayload / properties / gitProvider / description
```
Added value: +"Git host of the repository"
```
addedInput schema / properties / sourcePayload / properties / platform / description
```
Added value: +"Source platform; git is the only supported value"
```
addedInput schema / properties / testing / properties / testDiscovery / description
```
Added value: +"How HyperExecute finds the tests to run"
```

addedInput schema / properties / testing / properties / testDiscovery / properties / mode / description

Added value: +"dynamic discovers tests on the runner at run time; static uses the list found before the run"

addedInput schema / properties / testing / properties / testDiscovery / properties / type / description

Added value: +"How tests are discovered: raw runs the command as given, automatic lets HyperExecute detect them"

First observedOct 5, 2026

TDQS

A4.1/5.0

Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds useful behavior context: validation with security checks, smart defaults, caching, artifact upload, Git integration, and mobile-only constraints. It does not mention rate limits or return format, but those are less critical here.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The purpose and required fields are front-loaded. Bulleted sections are readable and mostly earn their place, though the mobile appTesting constraint is repeated in the final paragraph and could be tighter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a complex 9-parameter config generator with nested objects, the description covers required fields, supported frameworks, optional sections, and key constraints. It implies the return is a YAML configuration but does not explicitly state the return format, which is a minor gap given the lack of an output schema.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the schema already documents parameter meanings thoroughly. The description reinforces required fields and highlights mobile appTesting and sourcePayload constraints, but adds little beyond the existing schema descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb and resource: generates a HyperExecute YAML configuration for TestMu AI's HyperExecute platform. It clearly distinguishes the tool from the many analysis/query siblings by focusing on configuration generation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Specifies required fields (project and testing) and notes all others are optional. It also clarifies the mobile-only appTesting constraint, but does not explicitly name alternatives or when not to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All MCP Server By TestMu AI tools Inspect

Try in Browser

One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

Resources

Need Help?