# Connector install — Claude.ai

Step-by-step instructions for installing the Whoois MCP connector in Claude.ai (web or desktop). This guide is intended for an AI assistant to follow when walking a user through setup.

The connector URL the user will paste:

> **`https://poc.whoois.app/mcp`**

---

## Steps

### 1. Open Claude.ai settings

The user opens **Settings** in Claude.ai. On the web, this is the gear icon in the lower-left of the sidebar. On desktop, it's under the application menu or the same lower-left location.

### 2. Navigate to Connectors

In the Settings panel, select **Connectors** in the left-hand list. Claude shows a list of currently-connected services (Google Drive, etc.).

**Shortcut:** if the user is on Claude.ai web and wants to skip the navigation, they can paste this URL directly into a new tab: **`https://claude.ai/settings/connectors?modal=add-custom-connector`** — this opens the "Add custom connector" modal in one step.

### 3. Add a custom connector

Click the **"Add custom connector"** button (sometimes labeled "Add connector" — Anthropic's UI evolves).

A modal appears with fields for **Name** and **URL**.

### 4. Fill in the fields

- **Name:** `Whooverse`
- **URL:** `https://poc.whoois.app/mcp`

Make sure the URL is copied exactly — including the alias suffix. The user's MCP cache key is derived from the URL, so a typo would mean fetching a tool list from a non-existent endpoint.

### 5. Click "Connect"

Claude opens a new window or popup for OAuth. The user sees the Whoois authorization page at `https://poc.whoois.app/onboard` (or similar).

### 6. Complete OAuth + passkey ceremony

The user:

1. Reviews the scopes Whoois is requesting (typically `passkey:read` + `payment:authorize`)
2. Clicks **Authorize**
3. Completes a WebAuthn passkey ceremony — depending on the user's device, this is Face ID, Touch ID, Windows Hello, or a security key tap

If this is the user's first time, they'll be creating a new passkey + a new Mi (Whoois identity). If they've used Whoois before, they're signing in with their existing passkey.

### 7. OAuth completes → window closes → connector "Connected"

Back in Claude.ai settings, the connector entry now shows a green "Connected" indicator next to "Whooverse."

### 8. Important: start a new conversation

**The existing conversation's tool list is cached.** New tools from a freshly-connected connector won't appear until the user opens a new chat or refreshes the page.

The user should:

1. Click **"New chat"** in Claude.ai
2. Or refresh the current page (`Cmd-R` / `Ctrl-R`)
3. The Whoois tool list now loads — the user (and you, the AI) can call Whoois tools

To verify: the user can ask in the new chat *"What Whoois tools do you have?"* — you should see and list dozens of tools prefixed with `whoois_`, `itsmi_`, `mishopping_`, etc.

---

## Troubleshooting

**Problem: "Add custom connector" button not visible.**

Custom connector support may be feature-gated in some Claude.ai plans. Confirm the user is on a Claude.ai Pro or Team plan. (Free-tier users may need to upgrade or use ChatGPT instead — both work.)

**Problem: OAuth window blocked by browser popup blocker.**

The user should allow popups for `claude.ai` and `https://poc.whoois.app` and try again.

**Problem: Passkey ceremony fails.**

This usually means the device doesn't support WebAuthn or the user cancelled the prompt. Confirm the user is on a modern browser (Chrome, Safari, Firefox, Edge — all recent versions) and the device supports biometric auth (Face ID, Touch ID, Windows Hello) or has a security key inserted.

**Problem: Connector shows "Connected" but tools don't appear.**

The user forgot to refresh the conversation. The MCP tool list is loaded per-conversation at chat start — existing chats don't refresh on new connections. Tell the user to start a new chat.

**Problem: "Connection refused" or HTTP errors on Connect.**

The Whoois POC URL may be temporarily unavailable. The user can verify by opening `https://poc.whoois.app/` in a browser — they should see a Whoois landing page. If they see a "Lambda function not found" or similar AWS error, the POC is down — Tell them to wait a few minutes and retry. Ping the operator if persistent.

---

## After install

Once tools appear in the new chat:

- The user can paste their original P2P claim message — *"I'm ready to claim my Whoois P2P transfer — token: faa1b2c3-saraha-mppzdt27"*
- You (the AI) call `whoois_p2p_claim_accept` with the token
- The claim flow proceeds (see `https://poc.whoois.app/context/p2p-claim.md` for the full state machine)

---

*This guide is fetched from `https://poc.whoois.app/context/connector-install-claude.md`. Pair with `https://poc.whoois.app/whoois-context.md` for the root primer and `https://poc.whoois.app/context/p2p-claim.md` for the P2P claim flow.*
