Hosted MCP access
Connect your AI client to Uthana at https://mcp.uthana.com/mcp and sign in with
your Uthana account. No installation or API key is needed for hosted access.
The open-source local connector is also
available with a Uthana API key.
Connect Claude or Codex to your existing Uthana account to find characters, create and edit motion, and download results through your agent. You sign in to Uthana and choose the permissions to grant during setup. Your account's balance and the same prices as the Uthana app and API apply; see Costs and spending.
You can give your agent files through the file portal or a supported attachment integration. Your agent can retrieve exported files directly and provide links for you to download or view the results.
Connect with Codex
Desktop
- Open Plugins, choose Add, then Add MCP server. Older Codex app versions show this under Settings → MCP servers → Add server.
- Enter Uthana as the name, choose the remote Streamable HTTP option, and enter
https://mcp.uthana.com/mcpas the server URL. - Save the server, choose Authenticate, sign in to Uthana, and approve the requested permissions.
- Restart Codex if the Uthana tools do not appear after sign-in.
These steps are for the Codex app and CLI. See Codex MCP setup for the current client UI.
CLI
Run this command in your terminal:
codex mcp add uthana --url https://mcp.uthana.com/mcp
Codex detects that Uthana uses sign-in and opens the Uthana sign-in page in your browser. If the browser does not open, copy the link the CLI prints. Complete sign-in and consent there; the command then reports Successfully logged in. If you skip or cancel sign-in, run codex mcp login uthana later to finish it. codex mcp list shows whether Uthana is signed in.
Codex CLI asks you to approve each Uthana action that changes something, such as an export. If you run Codex with approvals turned off (--ask-for-approval never), those actions are refused.
Connect with Claude
Desktop, including Claude Code in the desktop app
- Open Customize → Connectors in the Claude desktop app. Older app versions may show this under Settings → Connectors.
- Choose Add, then Add custom connector. Name it Uthana, enter
https://mcp.uthana.com/mcpas the server URL, and choose Continue. - On the next screen, keep the detected defaults: Sign in now for authentication and Use Claude's published identity for the OAuth client. Leave request headers empty and choose Add.
- Sign in to Uthana in the browser window that opens and approve the permissions. Until you finish, Claude may show Connection issue for the connector; it clears once sign-in completes.
- Start a new chat. Uthana is usually already enabled there; if not, open + → Connectors and turn it on.
See Claude Code desktop connectors and Claude's custom connector guide. Organization-managed accounts may require an owner to add the connector first.
CLI (Claude Code)
Run this command in your terminal:
claude mcp add --transport http uthana https://mcp.uthana.com/mcp
This adds Uthana for the current project only. To make it available in every project, add -s user before uthana. Add it in one scope only: adding it to both creates two entries with the same name.
claude mcp list then shows Uthana as Needs authentication. Open Claude Code, run /mcp, select Uthana, and complete browser sign-in and consent. See Claude Code MCP setup.
Web (claude.ai)
Open Customize → Connectors on claude.ai, add a custom connector named Uthana, and enter https://mcp.uthana.com/mcp. Keep the detected defaults (Sign in now, Use Claude's published identity), then complete Uthana sign-in and consent. Enable Uthana from + → Connectors in your conversation if it is not already on. Organization-managed accounts may require an owner to add it first.
Claude desktop and claude.ai share your connector list: a connector added in one appears in the other, already signed in.
Connect with Cursor
Add this entry to .cursor/mcp.json for the current project, or ~/.cursor/mcp.json to make it available across projects:
{
"mcpServers": {
"uthana": {
"url": "https://mcp.uthana.com/mcp"
}
}
}
Open Cursor's MCP settings, find Uthana, and use its sign-in action to connect your Uthana account and approve the requested permissions. No API key, custom headers, or manually supplied OAuth client ID is needed. See Cursor MCP setup for the current client UI.
Other clients
Use a client that supports remote MCP servers over Streamable HTTP with OAuth sign-in. Add https://mcp.uthana.com/mcp as the server URL, then follow your client's sign-in instructions. The client must discover the sign-in details from the server and register itself automatically; Uthana does not issue manual OAuth client IDs or secrets. The permissions requested are read access (mcp:read) and write access (mcp:write) to your Uthana account's characters and motions.
You can also run the connector on your own computer using a Uthana API key. Follow the local installation guide for installation and client configuration.
Client compatibility
Tested results for each client. Verified means we completed that step in that client on the date shown. Not supported means it does not work today. Not yet verified means we have not tested it; it may still work.
| Client | Hosted sign-in | Local option | Chat attachment reaches Uthana | Preview shown in chat | Agent fetches exported file | Tested version / date | Known limitations |
|---|---|---|---|---|---|---|---|
| Claude desktop | Verified | Not yet verified | Not supported: use the file portal | Verified: still preview frame | Not supported by default: Claude's network settings block mcp.uthana.com; the download link works in your browser | 4.16336.0, 2026-11-04 | "Connection issue" shows until sign-in finishes. Re-adding after removal reconnects to the same account without a new sign-in |
| Claude web (claude.ai) | Verified (shares the desktop connector) | Not supported (runs no local servers) | Not supported: use the file portal | Not yet verified | Not supported by default: same network block as desktop | 2026-11-04 | Connector list is shared with Claude desktop |
| Claude Code CLI | Not yet verified | Verified: server connects (2026-11-04) | Not supported: use the file portal | Not yet verified | Not yet verified | 2.1.317, 2026-11-04 (setup commands only) | Add Uthana in one scope only |
| Codex desktop | Verified (existing connection; fresh setup not yet verified) | Not yet verified | Not yet verified | Verified: still preview frame | Verified: downloaded and checksum-matched after approving network access | 26.1029.61003, 2026-11-04 | Menu moved from Settings to Plugins in recent versions |
| Codex CLI | Verified | Not yet verified | Not supported: use the file portal | Not yet verified | Not yet verified | 0.166.0-alpha.6, 2026-11-04 | codex mcp add starts sign-in immediately; exports need approval |
| Cursor | Not yet verified | Not yet verified | Not supported: use the file portal | Not yet verified | Not yet verified | Not yet tested |
"Chat attachment reaches Uthana" is about files you attach in the chat itself. The hosted server accepts files from the file portal and from ChatGPT's own attachment links only, so files attached in the clients marked Not supported never reach Uthana, even when the client shows a paperclip. Claude accepts the attachment and can read it itself, but it cannot pass it to Uthana. The file portal works with every client: upload there, then paste the upload details into your request. Your agent cannot check an uploaded file on its own before using it; it reads the file when you ask it to create something from it.
Verify your connection
In your chosen client, ask:
Show my Uthana account's available balance and allowances. Don't create or change anything.
This is a read-only check that also works for a new account with no uploaded characters or motions. No manual OAuth client ID, client secret, or API key is needed for hosted setup. Signing into the file portal does not authorize a separate client.
This check is free. A file upload alone does not generate motion. Normal client tool and network approvals may still appear.
What the answer means
- Balance and allowances shown: you are connected. This check only proves the connection and sign-in; it does not test uploads, previews, downloads, or switching accounts. See Client compatibility for what has been tested in your client.
- A zero balance: you are connected, but generating motion needs credit. Add credit in your Uthana account settings; nothing in the connection needs to change.
- "Account linking is required" or a sign-in error: the server is added but your account is not linked. Use your client's Connect or Authenticate action, finish signing in, and ask again.
- The agent has no Uthana tools: Uthana is not enabled in this chat. Turn it on in the chat's tools or connectors menu, or start a new chat. If the tools are still missing, restart the client once.
Costs and spending
Hosted access uses the same prices and the same balance as the Uthana app and API, listed on uthana.com/pricing. There is no extra fee for the MCP or per agent call. Your AI client provider's own charges, if any, are separate.
- Charged: generating motion from text or video, locomotion, stitching and looping (per second of generated motion), auto-rigging an unrigged character ($0.15), and generating a character ($0.75). For example, a four-second Text-to-Motion 3.0 motion is estimated at $0.40 ($0.10 per second).
- Free: checking your balance, listing and searching your own characters and motions, cost estimates, previews, trimming, uploading an already-rigged character, exporting a motion you own onto any of your characters, and fresh links to an existing export.
- Account types: pay-as-you-go accounts, including every new account, pay from one balance; new accounts start with $5 of free credit, spent at the normal rates. Older subscription plans are not charged per operation; instead, new exports count against their monthly download allowance, measured in seconds of motion.
Ask your agent to "estimate only" and it creates nothing. Ask it to "estimate, then generate" and it goes ahead with the work you named. A budget you give your agent, such as "only if it costs at most $0.50", is an instruction the agent follows. Uthana does not enforce per-request budgets. Your agent reports estimates; the exact charge for each operation is in your account's transaction history. If your balance runs out, add credit there and ask your agent to continue the same task. The charging reference lists every tool.
Upload files for your agent
Tar, Ava, and Manny (also called Manny Fingers) are available to every Uthana user. You can use these characters without uploading your own.
To use your own files:
- Open the file portal and sign in with the same Uthana account you connected to your agent.
- Upload your file. Videos for video-to-motion can be MP4, MOV, or WebM up to 128 MiB. Characters can be FBX or GLB up to 30 MiB.
- Copy the upload details shown on the page into your conversation and tell your agent what to do with the file, for example: "Create a motion from the video I uploaded: upload details."
Uploading a file only stores it for your account. It does not create a character or generate motion, and it costs nothing. Your agent creates the character or motion when you ask it to, and that step uses credits at the normal prices.
Files you attach directly in the chat do not reach Uthana in Claude, Claude Code, Codex CLI, or Cursor; see Client compatibility. If your agent says it cannot use an attachment, upload the file through the portal instead. If you run the local connector, it reads files from the input folder you configure instead of the portal.
Download and view your results
Your agent can give you four kinds of result. They are different things:
- Preview in chat: preview frames or a short animation shown in the conversation, for checking a motion before you export it. Some clients cannot display them; ask for the viewer link instead.
- Uthana viewer link: opens the motion in the Uthana app, where it stays saved in your account. You can play, retarget, and export it again later.
- Download link: a temporary link to an exported file (FBX, GLB, or BVH). It expires after 15 minutes; see below.
- Downloaded file: the exported file itself, when your agent fetches the download link for you, for example into a project folder.
Ask your agent to download a motion in your preferred format, for example:
Download this motion as a GLB.
Your agent can fetch the file directly from the download link; you do not need to copy passwords, API keys, or sign-in details into the conversation. It can also give you a link to download the file yourself or open the motion in Uthana. Your client's normal tool or network approval prompts may still appear.
Download links expire after 15 minutes. If a link expires, ask your agent for a fresh link to the same file. Getting a new link or fetching an already exported file does not create another export or charge you again. Exporting a motion you own is free; on older subscription plans, a new export counts against the monthly download allowance.
Keep download links private: anyone with a working link can download that file.
If Claude connects but cannot download a file
Claude's connector and its file-download environment have separate network
permissions. If a download reports a network or proxy block, allow
mcp.uthana.com in Claude's network-access settings. For managed accounts,
your administrator may need to update those settings. See
Claude's network-access guide.
After changing the setting, ask your agent for a fresh link to the same file and retry the download. You can also open that link in your browser to download the file yourself. Do not request another export just to retry a blocked download.
Reconnect or recover an interrupted task
If your connection expires, use your client's Connect or Authenticate action and sign in to Uthana again. If a sign-in attempt expires or is cancelled, choose Start again. If sign-in is temporarily unavailable, wait and try again. Reconnecting does not affect your characters, motions, or exports; ask your agent for them instead of creating them again.
If you lose the connection while a task is running, ask your agent to check the existing task and retrieve its result before starting anything again. An interruption does not necessarily mean the task failed, and starting it again could incur another charge.
Disconnect or switch accounts
Removing Uthana from a client stops that client from using your Uthana account. It does not delete your characters, motions, uploads, or exports; they stay in your Uthana account.
- Claude desktop and claude.ai: open Customize → Connectors (older versions: Settings → Connectors) and select Uthana. Choose Disconnect to sign Claude out of Uthana; the connector stays, and Connect opens the Uthana sign-in in your browser again. To take the connector away entirely, open the ⋯ menu next to Disconnect and choose Remove. Because the connector list is shared, this removes it from both.
- Claude Code CLI: run
claude mcp remove uthana. If you added it with-s user, runclaude mcp remove uthana -s user. - Codex desktop: open Plugins, select Uthana, and remove it.
- Codex CLI: run
codex mcp logout uthanato delete the saved sign-in, thencodex mcp remove uthanato remove the server. Adding it again asks you to sign in again. - Cursor: remove the
uthanaentry frommcp.json, or remove it in Cursor's MCP settings.
To switch accounts in Codex CLI, remove Uthana, add it again, and sign in with the other account. The sign-in page uses your uthana.com browser session, so sign out of uthana.com first, or complete sign-in in a private window. In Claude, removing and re-adding Uthana reconnects to the same account without asking you to sign in, so it does not switch accounts. Use Disconnect and then Connect instead; if the sign-in does not offer the other account, contact support. Uthana does not show your email address through the connector; to check which account a client is using, compare the balance it reports with your account page on uthana.com.
Signing out of the file portal signs you out of that page only.
Get help
Contact support@uthana.com. Include your client name and version, your operating system, the approximate time, the error message, and any request or job ID your agent reported. Do not send passwords, API keys, sign-in links, download links, or private file contents.