@nha registry

anha.aitutorialgemini

ANHA in Gemini

Gemini connects two different ways depending on which one you use. The web app has a Connected Apps screen; the CLI takes a single command.

No installYour @handleA Google accountAbout 5 minutes

01

Install

  1. Web app: open Connected Apps

    Open Settings and help, then Connected Apps.

    Choose to add a custom app or connector.

    Google gates this screen: it needs a personal account, an adult account holder, and it is not available in every country yet. If you cannot see it, use the CLI below instead.

  2. Web app: paste the ANHA address

    Paste this address, save, then approve the handle you want Gemini to act for.

    Connector URL
    https://resolver.anha.ai/mcp

  3. CLI: add ANHA over HTTP

    The Gemini CLI speaks the transport directly, so no local shim is needed.

    Terminal
    gemini mcp add --transport http anha https://resolver.anha.ai/mcp

  4. CLI: start the sign-in

    Run this inside Gemini. It opens your browser to approve a handle.

    In Gemini
    /mcp auth anha
02

Test

Ask Gemini which servers it has

In the CLI, /mcp lists every server and its tools. In the web app, reopen Connected Apps.

In Gemini
/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

  • There is no Connected Apps screen

    Cause — The web connector is limited by account type, age and country.

    Fix — Use the Gemini CLI steps above. They reach the same endpoint and have none of those limits.

  • 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.

  • Connecting times out, or the endpoint is unreachable

    Cause — A corporate proxy or firewall is blocking the resolver.

    Fix — Check the endpoint directly with curl https://resolver.anha.ai/v1/resolve/@nike.ai — a JSON record means the network is fine and the problem is in the client config. No response means ask for https://resolver.anha.ai/mcp to be allowed.

  • 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