ANHA in GLM
GLM has no connector screen of its own, and Z.ai's MCP calling sends only fixed headers, which cannot carry the browser sign-in ANHA needs. So you point an agent app at ANHA and choose GLM as that agent's model.
Install
Pick an agent that supports MCP
Any of the terminal guides here will do — OpenClaw, Hermes, Codex or Qwen Code.
Install ANHA in that agent by following its guide.
See the terminal guidesChoose GLM as the model
In the agent's model settings, select GLM and supply your Z.ai API key.
The agent holds the ANHA connection; GLM is only the model answering through it.
Writing your own program instead?
Skip the agent entirely and call the REST rail directly. The tool definitions are public and need no sign-in to read.
Build your own agentTool definitionshttps://resolver.anha.ai/tools.json
Test
Check the agent sees ANHA
Run whichever list command your agent provides — the ANHA tools belong to the agent, not to GLM.
You should see
anha connected 8 toolsThen 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.”
Troubleshoot
- You cannot find an MCP or connector setting in GLM itself
Cause — There is not one. This is expected, not a configuration mistake.
Fix — Connect ANHA to the agent app and select GLM as its model, as above.
- 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.
- 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.