@nha registry

anha.aitutorialclaude

ANHA in Claude

Claude speaks the MCP transport ANHA serves directly, so there is nothing to install. You paste one address into its connector settings and approve the handle you want it to act for.

No installYour @handleA Claude accountAbout 3 minutes

01

Install

  1. Open your connector settings

    In Claude, open Settings and find Connectors.

    Choose Add custom connector.

  2. Paste the ANHA address

    Name it ANHA so you recognise it later.

    Paste this address into the URL box and save.

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

  3. Sign in and approve

    Claude opens an ANHA sign-in page. Use the email you registered your handle with.

    Pick the handle you want Claude to act for, then choose Allow.

    The approval screen lists only handles registered to the email you sign in with. Signing in with a different address shows an empty list.

02

Test

Check the connector reports Connected

Reopen Settings and Connectors. ANHA should be listed as connected, with its tools enabled.

You should see

ANHA        Connected
tools       8 enabled

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 look up @nike.ai and tell me what it can do.”

03

Troubleshoot

  • The approval page shows no handles

    Cause — You signed in with an email address that does not own a handle.

    Fix — Sign out of the approval page and sign in with the email you used at registration. If you have not registered yet, do that first.

  • 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