atest

You can run and connect to the MCP server for atest to manage and execute tools from a centralized MCP registry. It supports both HTTP-based MCP access and a local stdio runner, making it easy to integrate with clients, Docker, or command-line workflows.

How to use

To use the MCP server with a client, start the server to expose an endpoint you can connect to and then run tools through the MCP interface. You can run the server in standard HTTP mode for remote clients or in stdio mode for local automation pipelines. The server provides an HTTP endpoint at a local URL and a stdio runner you can invoke directly from your scripts.

How to install

Prerequisites: ensure you have a modern shell, Docker, and Node.js available if you plan to use the provided runnable commands.

// Start the MCP server using a gRPC/HTTP port
atest-store-mcp server --runner-address 127.0.0.1:64385

// Run the MCP server in Docker (exposes port 7845)
docker run -p 7845:7845 ghcr.io/linuxsuren/atest-mcp-server --runner-address 127.0.0.1:64385

// Run the MCP server via npx (stdio mode)
npx atest-mcp-server-launcher@latest server --mode=stdio --runner-address=localhost:64385

Additional content

Configuration examples show both an HTTP-based MCP server endpoint and a local stdio-based launcher. Use HTTP for remote clients and stdio for local automation. You can choose the mode with the --mode flag when starting the server.

// Example HTTP MCP server configuration
{
  "mcpServers": {
    "atest": {
      "name": "atest",
      "type": "http",
      "description": "The MCP server of atest",
      "isActive": true,
      "url": "http://localhost:7845",
      "args": []
    }
  }
}

// Example stdio MCP server configuration
{
  "mcpServers": {
    "atest_mcp_stdio": {
      "name": "atest-mcp-stdio",
      "type": "stdio",
      "description": "",
      "isActive": true,
      "command": "atest-store-mcp",
      "args": [
        "server",
        "-m=stdio",
        "--runner-address=localhost:64385"
      ]
    }
  }
}

Build and publish utilities mentioned include standard build and packaging commands for the MCP ecosystem. You can build the project with a make-based workflow and package with npm tooling. When ready to publish, you can log in to npm and publish, or use the MCP publisher tooling to publish to GitHub or npm registries.

# Build the binary
make build

# Package with dxt if needed
npm install -g @anthropic-ai/dxt
dxt pack

# Publish to npm
npm login --registry https://registry.npmjs.com
npm publish --registry https://registry.npmjs.com

# Publish MCP package (example tool)
mcp-publisher login github
mcp-publisher publish

Available tools

build

Build the MCP server binary or package to prepare for distribution or local use.

publish

Publish MCP client/server packages to registries or their hosting platforms using the MCP publishing workflow.

launcher

Launch MCP server in stdio mode via a launcher that communicates with a local runner.