ANHA in Qwen

Qwen Code reads MCP servers from a JSON settings file in your home directory. The Qwen Chat desktop app has an MCP settings screen instead.

Config fileYour @handleNode.js 20+About 8 minutes

01

Install

  1. Qwen Code: open the settings file

    Create ~/.qwen/settings.json if it is not already there.

    Path
    ~/.qwen/settings.json
  2. Qwen Code: add ANHA

    Add an mcpServers block. Merge it with what is already in the file rather than replacing the file.

    ~/.qwen/settings.json
    {
      "mcpServers": {
        "anha": {
          "command": "npx",
          "args": ["-y", "anha-mcp"]
        }
      }
    }
  3. Qwen Chat: use the MCP settings screen

    In the desktop app, open MCP settings and add a server.

    Paste this address and approve the handle when the browser opens.

    Server URL
    https://resolver.anha.ai/mcp
  4. Sign in

    Approve the handle you want Qwen to act for.

    Terminal
    npx -y anha-mcp login
02

Test

Check Qwen loaded the server

Start Qwen Code and list its tools; ANHA should be among them.

In Qwen Code
/mcp

You should see

anha    ready    8 tools

Then ask for something real

A passing check only proves the connection works. This proves the model can actually reach the tools.

Use ANHA to resolve @nike.ai and tell me what it can do.

03

Troubleshoot

  • The settings file is ignored

    Cause — The JSON is malformed — usually a trailing comma after the last entry.

    Fix — Paste the file into any JSON validator. Qwen Code skips a file it cannot parse without saying so.

  • No ANHA tools appear at all

    Cause — The config file was edited while the app was running, so it is still holding the old server list.

    Fix — Quit the app completely and start it again. Opening a new tab or window is not enough.

  • The tools are listed, but every call answers that you are not signed in

    Cause — The browser approval was closed before it finished, or you approved with an email address that owns no handle.

    Fix — Run npx -y anha-mcp login again and sign in with the same email you registered the handle under. If you have no handle yet, register one first — the approval screen has nothing to offer otherwise.

  • npx: command not found, or the package will not install

    Cause — Node.js is missing or older than v20, so npx is unavailable or refuses anha-mcp.

    Fix — Run node --version. Below v20, install the LTS build from nodejs.org and open a new terminal so the new PATH takes effect.

  • An order or payment just hangs

    Cause — This is not a fault. The merchant requires phone approval, so the call returns a pending status with a request id.

    Fix — Approve it on your phone. A human decision can take minutes, and the caller polls until it lands.

Still stuck?

Every guide shares the same sign-in and the same tools, so a fix on another platform often applies here too.

All twelve guides