atest

The MCP server for atest exposes a machine-parseable API that enables tooling to manage and interact with the atest-based testing ecosystem. You can run the server in stdio mode or via a container/loader workflow, connect to its gRPC runner at the configured address, and use MCP to discover available tools, configure workflows, and publish tooling through the MCP registry. Typical usage is to start the server with a specified runner address, then interact with it through the MCP protocol to request tools, open sessions, and drive automated tests.

Once running, you can leverage the available tools provided by the atest ecosystem (for example, HTTP-based test runners, or other tooling registered under the atest MCP server) and manage them through MCP operations like discovery, activation, and publishing. If you need to switch modes, you can start the server with --mode=sse to use Server-Sent Events style communication or --mode=stdio for a local standard input/output bridge, depending on your integration needs.

Prerequisites:

• Docker (optional, for containerized runs)
• Node.js / npm (optional, for npx launcher)
• Go tooling (optional, for building binary if you clone the repo and build locally)
• Access to the atest repository and the MCP server binary if you plan to run a prebuilt binary

Installation options:

Option A: Run with Docker

1. Pull and run the MCP server container: docker run -p 7845:7845 ghcr.io/linuxsuren/atest-mcp-server --runner-address 127.0.0.1:64385

2. The server will listen on 127.0.0.1:64385 inside the container and expose the MCP API on port 7845 externally as configured.

Option B: Use npx launcher (recommended for quick starts)

1. Ensure Node.js and npm are installed.

2. Start the MCP server with npx: npx atest-mcp-server-launcher@latest server --mode=stdio --runner-address=localhost:64385

3. The server will be started in stdio mode and listen on the specified runner address.

Option C: Run the stdio server binary directly (prebuilt or built locally)

1. Build or obtain the atest-store-mcp binary.

2. Run: atest-store-mcp server -m=stdio --runner-address=localhost:64385

3. The MCP server will start and listen for MCP interactions on the provided address.

Tips and common issues:

• The runner-address must be reachable by your MCP clients. Use localhost for local development, or an accessible network address in multi-host environments.
• When using stdio mode, the client communicates with the MCP server over standard I/O streams; ensure the integration wrapper captures and forwards these streams correctly.
• If you encounter port conflicts, choose a different --runner-address (e.g., --runner-address=127.0.0.1:64400).
• The baseUrl (http://localhost:7845) shown in docs is for the HTTP interface used by tooling to fetch metadata; ensure your network rules permit access to this URL if you rely on HTTP-based tooling.
• The MCP mode can be switched with --mode=[sse|stdio]. SSE mode is suitable for browser-capable clients and streaming APIs, while stdio mode is convenient for local, console-based workflows.
• When using Docker, keep in mind that port mappings (e.g., -p 7845:7845) expose the MCP HTTP interface; use the mapped port in your MCP client configuration.