
Atest Mcp Server
io.github.LinuxSuRenPublished by GitHub account LinuxSuRenv1.0.2Updated Oct 24, 2026
Auto-download & launch https://github.com/LinuxSuRen/atest-mcp-server
Overview
Runs the atest MCP server locally so an assistant can work with an atest test runner over gRPC.
- What you can do
- This is the MCP server component of atest, a testing tool. It is launched as a local process and connects to an atest runner at a gRPC address, exposing that runner to an AI assistant. It can run in stdio or SSE mode, and can also be started via Docker or npx. The README does not list individual tool names.
- When to use it
- Worth adding when you already use atest for testing and want an assistant to interact with your test runner from the same machine. It is not useful on its own, since it depends on a running atest runner.
- Requirements
- A local runtime: the atest-store-mcp binary, Docker, or the npm launcher atest-mcp-server-launcher via npx. A reachable atest runner gRPC address passed with --runner-address (for example 127.0.0.1:64385). Desktop only; no authentication or environment variables are declared.
Installation
In SourceWeft
- Open Atest Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This is the MCP server of atest.
Get started
Please start the MCP server with atest gRPC port.
or start in Docker
or start in npx
You can also set the MCP server mode with the --mode flag.
MCP Server
or as stdio mode:
How to build
You can build the binary with the following command:
You can build .dxt package with the following command:
How to publish
You can publish the package with the following command:
read more about mcp-publisher
Source: README.md at commit 4eac8c3
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.