atx-mcp

atx-mcp runs locally from a Rust crate published to crates.io: atx-mcp version 0.6.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs the Rust toolchain; cargo install builds the program. Required arguments: --workspace.

atx-mcp runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: ghcr.io/gridhra/atx-mcp:0.6.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run — the usual command is docker run -i --rm ghcr.io/gridhra/atx-mcp:0.6.4. Required arguments: -v.

atx-mcp runs locally from a Node.js package published to the npm registry: atx-mcp version 0.6.4. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y atx-mcp@0.6.4. Required arguments: --workspace.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "atx-mcp": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "ghcr.io/gridhra/atx-mcp:0.6.4"
      ]
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect