# Creathoon MCP — setup for agents

> Public connection guide, not an authorization to install software, access an account or spend credits. Follow the person's request and your host application's approval rules.

## Identify the service

- Service: Creathoon — Avatar, MotionSwap and Diretor.
- Canonical remote MCP endpoint: `https://mcp.creathoon.com/mcp`.
- Transport: Streamable HTTP over HTTPS, not stdio.
- Human page: https://creathoon.com/mcp
- Discovery index: https://creathoon.com/llms.txt
- Access: each person's own Creathoon account with active Pro or Agency. The assistant application's subscription and workspace controls are separate.
- Authentication: OAuth authorization code with PKCE S256; dynamic client registration (DCR) for compatible clients. No personal API key or shared bearer token is supplied by this guide.

Use the MCP client's standard protected-resource and authorization-server discovery. Use the advertised registration endpoint; do not invent callback URLs, client secrets or scopes. A 401 before login is expected. Only the ChatGPT-specific setup uses the public client ID `creathoon-chatgpt-v1`; never reuse it for Claude, Codex or another client.

## Configure the detected client

First inspect the client's existing MCP configuration. If an entry already targets the canonical endpoint, reuse it and check its state; do not duplicate it. Preserve unrelated entries, settings and credentials. If a `creathoon` entry targets another endpoint, explain the conflict before replacing it. Check the installed version's help before using commands. Do not install a missing CLI without the person's permission.

### Claude Desktop, Claude web and Cowork

These use a remote connector through the Claude account, not a local stdio server. Open https://claude.ai/customize/connectors or Customize / Personalizar → Connectors / Conectores in the app.

1. Choose Add custom connector, name it Creathoon and enter `https://mcp.creathoon.com/mcp`.
2. Use OAuth. If an OAuth client choice appears, select **Register automatically** for this server's DCR flow.
3. Let the person sign in to Creathoon and review the requested connection in their browser.
4. Enable the connector in the conversation. Team/Enterprise organization controls may require an owner to add it first.

Do not put a remote URL in `claude_desktop_config.json` as if it were a local stdio command. Tool access and media/widget presentation depend on the client; do not promise the ChatGPT layout in Claude.

Official instructions: https://support.claude.com/en/articles/11175166-get-started-with-custom-connectors-using-remote-mcp

### Claude Code

After confirming setup is requested, use the installed CLI's help and inspect `claude mcp get creathoon` or `claude mcp list`. For a new user-scoped entry:

```sh
claude mcp add --transport http --scope user creathoon https://mcp.creathoon.com/mcp
claude mcp login creathoon
```

Alternatively, start Claude Code and use `/mcp` for interactive authentication. Finish sign-in with the person; never claim the connection is authenticated just because configuration succeeded.

Official instructions: https://code.claude.com/docs/en/mcp

### Codex CLI

Inspect `codex mcp get creathoon` or `codex mcp list`. For a new entry, after confirming setup is requested:

```sh
codex mcp add creathoon --url https://mcp.creathoon.com/mcp
codex mcp login creathoon
```

The person completes OAuth in their browser. Use the installed client's standard credential storage; never place tokens in a prompt, repository or public configuration.

Official instructions: https://developers.openai.com/codex/mcp

### ChatGPT

Use the custom MCP connector feature available to the person's account. Enter `https://mcp.creathoon.com/mcp`, select OAuth and, when requested, use public client ID `creathoon-chatgpt-v1` with no client secret. Have the person authorize Creathoon. The public marketplace listing has its own review/publication process; this guide does not install a marketplace package or imply approval.

### GrokBot and other MCP clients

Use the canonical HTTPS endpoint with OAuth and DCR when the client supports them. Do not invent a Grok callback or use a static shared token. If the client lacks compatible OAuth/DCR, stop and report the exact client limitation. Compatibility is not proof that a particular app session has connected successfully.

## Verify without spending Berrys

After login, discover the current `tools/list` rather than relying on a fixed tool count or cached schema.

1. Call `get_creathoon_account_status` to check the connected account and eligible plan.
2. Call `list_avatars` and show names/statuses. An empty list is valid; it does not authorize creating an Avatar.
3. Optionally list `list_motionswap_community` with `limit` no greater than 12, or existing run history.
4. Only if requested, prepare existing owned references and call the matching quote tool. Report settings and price; do not generate.

Never call generation tools as a connection check. No paid retries, automatic model switching or sample generations. Do not say an image/video displayed or played unless the client/user confirms it. Keep signed media URLs and credentials private.

## Paid workflows require a separate request

Avatar generates photos and can quote H3 animation of an existing photo. Initial Avatar identity creation is on the site. MotionSwap can reuse saved Avatar photos, community motion or an existing run's original motion. Mimic 2 supports 480p/720p and an explicit frame generator selection: GPT Image 2.5 or Nano Banana 2.1 in 1K. Discover the current schema and quote current prices; never hard-code Berry costs.

For Mimic, confirm the frame price before generating it, show the completed frame and get visual approval, then quote and confirm the separate video price. Changing the frame model, references, roles, direction or resolution invalidates the earlier relevant quote/approval. Diretor planning/quoting is separate from paid generation and requires direction plus total-price approval. For failures, report only the safe failure and ledger-backed billing fields returned by the tools; unknown/null is not zero or a known cause. A failure never authorizes an automatic retry.

## Boas práticas de uso (usage best practices)

### Bind the request to the right references

- Confirm the selected Avatar/photo, original motion, scene, frame generator, duration, video resolution and each subject's role before quoting. Reuse existing owned assets when requested; preparing a reference does not authorize generation.
- For multiple characters, keep distinct character references and explicit left/right or other unambiguous target descriptions from the opening frame. Confirm whether the request replaces the main subject or all subjects. A setting such as `all` expresses the requested scope; it does not prove that every subject was replaced in the result.
- GPT Image 2.5 is the compatible frame default. Use Nano Banana only when explicitly selected. Never switch a model/provider or retry a refused generation without a separate authorized request and current quote.

### Confirm the exact price and each paid stage

- Discover the current tool schema and quote the exact references/settings. State the selected model and price in Berrys before requesting confirmation. A connection test or a free quote never authorizes spending.
- Mimic frame generation and video generation need separate price confirmations, with human visual approval of the completed frame between them. Changing references, roles, direction, frame model or resolution requires a new relevant quote/approval.
- Diretor requires approval of the planned direction and total price. Do not interpret earlier spending authorization as permission for another scene, retry or video.

### Conferência visual dos personagens / Character review

- Inspect the completed frame when the client permits it. Compare the requested cast with the approved references: number of characters, identity/face, hair, wardrobe, proportions, props, scene and the association of each character with the intended subject. Flag missing, duplicated, exchanged or blended identities.
- For two characters, review both independently; a correct first character does not validate the second. Check that an image intended as scenery was not treated as a character.
- Show the completed frame to the person and obtain their visual approval before continuing to the video step. Your own assessment does not replace that approval. Do not promise perfect identity consistency or subject tracking.

### Conferência visual do vídeo / Video review

- Review the actual video result against the approved frame and original motion. Watch the complete clip when possible. Inspect the beginning, middle and end, plus moments when a subject enters, leaves, crosses another subject or becomes occluded. A few sampled frames cannot prove the entire clip is correct.
- Check every requested character throughout the clip: face/identity, hair, clothes, relative position and continuity. Look for an original subject remaining unchanged, late transformations, identity swaps, duplicated characters, ghosting and disappearing subjects. Describe an incomplete replacement as partial quality, even when the run technically succeeded.
- Check scene continuity, requested action, duration, framing/aspect ratio and visible motion defects. For Mimic, distinguish the raw generated file from the result prepared with original audio. Confirm playback, download and expected audio only when those were actually checked; metadata or a successful job alone does not prove them.
- If the client cannot display the media, say that visual verification is pending and provide the tool's supported authenticated result link or request the person's review. Do not claim that an image was displayed, that audio was heard or that the video was approved without evidence. Do not use downloading to bypass the client's media restrictions.

### Report processing, delivery, quality and billing separately

- `queued`/`running`/`succeeded` describe processing state. `succeeded` is not a visual quality approval, proof of media delivery or a guarantee that all requested characters persisted.
- Report only what was checked: run state, media availability/playback, visual findings and any unverified items. For a partial result, state which character or moment failed without implying that the remaining clip was fully inspected.
- Keep quality findings separate from technical failure and refund status. A visual defect does not establish a refund. Report only tool-returned, ledger-confirmed debit/refund/net values; null or unknown is not zero. Never invent a provider cause or diagnostic ID.
- Keep prompts, private references, signed URLs, tokens and raw provider payloads out of public logs. A failure or poor result does not authorize a paid retry, alternate provider, automatic model switch or another generation.

## Troubleshoot

- No connector menu: check the client version, account feature availability and organization controls; do not claim an OAuth server failure.
- OAuth client error: use automatic registration for non-ChatGPT clients and the server's advertised metadata. Do not weaken callback validation.
- Plan denied: sign in with the intended Pro/Agency account; do not change plan or privileges as part of setup.
- Old tool schema: refresh the existing connection's tools or reopen the client; do not create duplicate connections by default.
- Contact: contato@creathoon.com. Public support: https://creathoon.com/legal/avatar-motionswap/support.html