Unitymcptest MCP

What unitymcptest-mcp MCP server does

The unitymcptest-mcp MCP server gives AI agents access to a hosted Unity-MCP testing workflow. It is designed for checking Unity scenes and returning structured results that can support review, debugging, and audit-oriented records. The service is remote and paid; the repository documents the hosted product rather than containing its private production implementation.

Four MCP tools are exposed:

• run_unity_playmode_check
• invoke_unity_method
• summarize_unity_failure
• export_unity_receipt

Together, these tools cover the documented test-loop workflow: run a check, call a Unity method, summarize a failure, and export a receipt. The available material does not define each tool's input schema or response fields, so those details should be confirmed through the service metadata or the MCP client's tool inspection.

How it works

The service exposes a Streamable HTTP MCP endpoint at https://unitymcptest.clauxel.com/mcp. An MCP client sends JSON-RPC requests to that endpoint and authenticates production calls with a bearer token. The hosted service also publishes server-card metadata at https://unitymcptest.clauxel.com/server-card.json.

Results are oriented toward review and record keeping. The description specifically identifies verdicts, receipts, usage logs, and audit-ready JSON as outputs or service concerns. This makes the unitymcptest-mcp MCP server relevant when an agent needs more than an informal text response from a Unity test run.

Setup and configuration

Access requires a paid plan. Start on the product website, choose a plan, and create or request an API token. Then add the MCP endpoint to a client that supports remote Streamable HTTP servers and configure the client to send the token as an HTTP authorization header:

Authorization: Bearer <token>

The documentation does not specify a required environment-variable name, client-specific configuration file, or local installation command. Unauthenticated browser requests to /mcp return a JSON error rather than exposing internal details.

Tools and capabilities

The documented tool surface consists of four operations. run_unity_playmode_check is the entry point for the named playmode-check workflow. invoke_unity_method provides the named Unity method-invocation operation. summarize_unity_failure handles the documented failure-summary step, while export_unity_receipt supports receipt generation.

The service also provides public server-card metadata and usage logs. Receipt-oriented JSON is a central output format, and the product is described as returning review-ready receipts for agent workflows.

Limitations and notes

The unitymcptest-mcp MCP server is not presented as a local Unity package or self-hosted implementation. The repository is a public documentation and directory-submission reference for the hosted service, and it does not include the private production source code.

Production use requires a bearer token issued through the product website and a paid plan. The provided documentation does not state which MCP clients support the endpoint by name, beyond requiring a client with Streamable HTTP support. It also does not document the tools' parameters, Unity project connection procedure, response schemas, rate limits, or plan-specific quotas. Confirm those details before building an automated pipeline around the service.